Webhooks allow you to build or set up integrations, such as App GitHubs or App 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 a Servidor de GitHub Enterprise instance, an organization, a specific repository, or a App 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 (Servidor de GitHub Enterprise instance, specific organization, or specific repository).
Events
Cuando configuras un webhook, puedes utilizar la IU o la API para elegir qué eventos te enviarán cargas útiles. El suscribirte únicamente a los eventos específicos que pretendes gestionar limita la cantidad de solicitudes HTTP a tu servidor. También puedes suscribirte a todos los eventos futuros y actuales. Predeterminadamente, los webhooks solo se suscriben al evento de carga. Puedes cambiar la lista de eventos a los que te suscribiste en cualquier 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
Cuando creas un webhook nuevo, te enviaremos un evento de ping sencillo para informarte que configuraste el webhook correctamente. Este evento no se almacena, así que no se puede recuperar a través de la API de Eventos. Puedes activar nuevamente un ping si llamas a la terminal Hacer ping a un webhook del repositorio.
For more information about the ping event webhook payload, see the ping event.