c116efe725
* New Crowdin translations by Github Action * Revert broken translated files to English * Revert broken translations * Revert broken translations * Revert more broket translations * Revert broken translation * Increase Node memory limit for running Jest * Allow Node to use more memory for Jest * Increase Node memory limit for running Jest Co-authored-by: Crowdin Bot <support+bot@crowdin.com> Co-authored-by: Chiedo <chiedo@users.noreply.github.com> Co-authored-by: James M. Greene <JamesMGreene@github.com>
1.7 KiB
title, intro, redirect_from, versions
| title | intro | redirect_from | versions | |||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Testing webhooks | Review your webhook deliveries on {% data variables.product.prodname_dotcom %}, including the HTTP Request and payload as well as the response. |
|
|
Now that you've configured your local server, 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 delivery 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.
