This guide will use that API to demonstrate a setup that you can use.

In our scenario, we will:

* Merge aPull Request

* When the CI is finished, we'll set thePull Request's status accordingly.

* When thePull Request is merged, we'll run our deployment to our server.

* Merge apull request

* When the CI is finished, we'll set thepull request's status accordingly.

* When thepull request is merged, we'll run our deployment to our server.

Our CI system and host server will be figments of our imagination. They could be

Heroku, Amazon, or something else entirely. The crux of this guide will be setting up

to configure ngrok to start listening for that, too.

In order for this server to work, we'll need to set a repository up with a webhook.

The webhook should be configured to fire whenever aPull Request is created, or merged.

The webhook should be configured to fire whenever apull request is created, or merged.

Go ahead and create a repository you're comfortable playing around in. Might we

suggest[@octocat's Spoon/Knife repository](https://github.com/octocat/Spoon-Knife)?

After that, you'll create a new webhook in your repository, feeding it the URL

* Deployment

* Deployment status

These are the events {{ site.data.variables.product.product_name }} will send to our server whenever the relevant action

occurs. We'll configure our server to*just* handle whenPull Requests are merged

occurs. We'll configure our server to*just* handle whenpull requests are merged

right now: