f272eec944
* ran script/remove-unused-assets.js (manually removed unused variables printed by the script) * package-lock * turn elsif into two ifs to prepare for running Liquid deprecation script * ran script/remove-deprecated-enterprise-version-markup.js --release 2.14 (ONLY UPDATES LINE BREAKS ETC.) * ran script/remove-deprecated-enterprise-version-markup.js --release 2.15 * ran script/remove-deprecated-enterprise-version-markup.js --release 2.17 * ran script/remove-deprecated-enterprise-version-markup.js --release 2.18 * update hardcoded test * Update content/github/collaborating-with-issues-and-pull-requests/filtering-files-in-a-pull-request.md Co-authored-by: Matt Pollard <mattpollard@users.noreply.github.com> * add currentVersion is NOT free-pro-team to conditional, to make sure the deprecation script does the right thing when it is time to deprecate 2.21 Co-authored-by: Matt Pollard <mattpollard@users.noreply.github.com>
44 lines
1.6 KiB
Markdown
44 lines
1.6 KiB
Markdown
---
|
|
title: Testing webhooks
|
|
intro: 'Review your webhook deliveries on {% data variables.product.prodname_dotcom %}, including the HTTP Request and payload as well as the response.'
|
|
redirect_from:
|
|
- /webhooks/testing
|
|
versions:
|
|
free-pro-team: '*'
|
|
enterprise-server: '*'
|
|
---
|
|
|
|
|
|
Now that you've [configured your local server](/webhooks/configuring/), you might
|
|
be interested in pushing your code to the limits. To that end, GitHub's webhooks
|
|
view provides some tooling for testing your deployed payloads.
|
|
|
|
### Listing recent deliveries
|
|
|
|
Every webhook has its own "Recent Deliveries" section, which lists, at a glance whether a deployment was successful (green check) or failed (red x). You can also identify when each delivery was attempted.
|
|
|
|
{% data variables.product.product_name %} keeps a log of each webhook delivery for {% if currentVersion == "free-pro-team@latest" %} 30 {% else %} 8 {% endif %} days.
|
|
|
|
|
|
|
|
### Digging into results
|
|
|
|
By expanding an individual delivery, you'll be able to witness *precisely*
|
|
what information GitHub is attempting to send to your server. This includes
|
|
both the HTTP Request and Response.
|
|
|
|
#### Request
|
|
|
|
The webhook delivery view provides information on which Headers were sent by GitHub.
|
|
It also includes details about the JSON payload.
|
|
|
|
|
|
|
|
#### Response
|
|
|
|
The response tab lists how your server replied once it received the payload from
|
|
GitHub. This includes the status code, the headers, and any additional data
|
|
within the response body.
|
|
|
|
|