Webhooks allow you to build or set up integrations, such as aplicativo GitHubs or aplicativo OAuths, which subscribe to certain events on GitHub.com. When one of those events is triggered, we'll send a HTTP POST payload to the webhook's configured URL. Webhooks can be used to update an external issue tracker, trigger CI builds, update a backup mirror, or even deploy to your production server. You're only limited by your imagination.
Webhooks can be installed on GitHub Enterprise, an organization, a specific repository, or a aplicativo GitHub. Once installed, the webhook will be sent each time one or more subscribed events occurs.
You can create up to 250 webhooks for each event on each installation target (GitHub Enterprise Server instance, specific organization, or specific repository).
Events
Ao configurar um webhook, você pode usar a interface do usuário ou API para escolher quais eventos enviarão cargas. Assinar apenas os eventos específicos que pretende gerenciar limita o número de solicitações HTTP para o seu servidor. Você também pode assinar todos os eventos atuais e futuros. Por padrão, os webhooks são apenas inscritos no evento de push. Você pode alterar a lista de eventos assinados a qualquer momento.
Each event corresponds to a certain set of actions that can happen to your organization and/or repository. For example, if you subscribe to the issues event you'll receive detailed payloads every time an issue is opened, closed, labeled, etc.
See "Webhook event payloads" for the list of available webhook events and their payloads.
Ping event
Ao criar um novo webhook, enviaremos um simples evento de ping para informar que você configurou o webhook corretamente. This event isn't stored so it isn't retrievable via the Events API endpoint.
For more information about the ping event webhook payload, see the ping event.