caaee7a124
* Add back changes from prior to purge * Manually fix some invalid Liquid * Updoot render-content * Improve test messages to show correct output * Run el scripto * Pass the remaining test
1.3 KiB
title, redirect_from, intro, versions
| title | redirect_from | intro | versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| About webhooks |
|
Webhooks provide a way for notifications to be delivered to an external web server whenever certain actions occur on a repository or organization. |
|
{% tip %}
Tip: {% data reusables.organizations.owners-and-admins-can %} manage webhooks for an organization. {% data reusables.organizations.new-org-permissions-more-info %}
{% endtip %}
Webhooks can be triggered whenever a variety of actions are performed on a repository or an organization. For example, you can configure a webhook to execute whenever:
- A repository is pushed to
- A pull request is opened
- A {% data variables.product.prodname_pages %} site is built
- A new member is added to a team
Using the {% data variables.product.product_name %} API, you can make these webhooks update an external issue tracker, trigger CI builds, update a backup mirror, or even deploy to your production server.
To set up a new webhook, you'll need access to an external server and familiarity with the technical procedures involved. For help on building a webhook, including a full list of actions you can associate with, see "Webhooks."