@@ -13,25 +13,24 @@ information about activity in a repository. Webhooks can trigger across several
1313different actions. For example, you can fire a payload of information any time
1414a commit is made, a repository is forked, or an issue is created.
1515
16- In this tutorial, our hook will be responsible for listing out how popular our
16+ In this tutorial, our webhook will be responsible for listing out how popular our
1717repository is, based on the number of Issues it receives per day.
1818
19- Creating a hook is a two-step process. You'll first need to set up how you want
20- your hook to behave through GitHub--what events should it listen to, and what
21- fields (if any) should be passed along. After that, you'll manage how to receive
22- the payload on your server.
19+ Creating a webhook is a two-step process. You'll first need to set up how you want
20+ your webhook to behave through GitHub--what events should it listen to. After that,
21+ you'll set up your server to receive and manage the payload.
2322
2423## Setting up a Hook
2524
26- To set up a hook on GitHub, head over to the ** Settings** page of your repository,
25+ To set up a webhook on GitHub, head over to the ** Settings** page of your repository,
2726and click on ** Webhooks & services** . After that, click on ** Add webhook** .
2827
2928You'll be presented with a page that lists all the capabilities your webhook
3029can take advantage of. We'll go through each of these below.
3130
3231## Payload URL
3332
34- This is the server endpoint that will receive the hook payload.
33+ This is the server endpoint that will receive the webhook payload.
3534
3635Since we're developing locally for our tutorial, let's set it to ` http://localhost:4567/payload ` .
3736We'll explain why in the [ Configuring Your Server] ( /hooks/configuring/ ) docs.
@@ -43,15 +42,15 @@ Choose the one that best fits your needs. For this tutorial, the default format
4342
4443## Events
4544
46- Events are at the core of webhooks. These hooks fire whenever a certain action is
45+ Events are at the core of webhooks. These webhooks fire whenever a certain action is
4746taken on the repository, which your server's payload URL intercepts and acts upon.
4847
49- A full list of hooks , and when they execute, can be found in [ the hooks API] [ hooks-api ] reference.
48+ A full list of webhook events , and when they execute, can be found in [ the webhooks API] [ hooks-api ] reference.
5049
51- Since our hook is dealing with Issues in a repository, we'll click on ** Issues** ,
50+ Since our webhook is dealing with Issues in a repository, we'll click on ** Issues** ,
5251and toggle the options there.
5352
54- When you're finished, click on ** Add webhook** . Phew! Now that the hook is created,
53+ When you're finished, click on ** Add webhook** . Phew! Now that the webhook is created,
5554it's time to set up our local server to test the webhook. Head on over to
5655[ Configuring Your Server] ( /hooks/configuring/ ) to learn how to do that.
5756
0 commit comments