How to address the issue of a particular GitHub Integration being not reachable #24547
-
What happens in general if a GitHub integration is down. The pull request seems to go through when the app is not up. EDIT 1 : START I was just wondering that since webhooks are sent from GitHub side to the webhook url that we configure in the app setting, is there a way for GitHub to notify users if the webhook url is not reachable. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
👋 hi, @akmalick. Thanks for the question.
GitHub only communicates with your App via Webhooks, sending HTTP requests to a URL of your choice. As the owner of the App you can access a list of recent Webhook deliveries and see the payload we sent. If your Webhook URL does not respond with a 200, then the delivery is marked as failed. You have the option to “Redeliver” any Webhook, which will send the request again. This information is only visible to the owner of the App. GitHub never displays this information (or anything else about whether your App is functioning correctly) to people who have installed your App. Depending on the volume of traffic your App receives, it might be sufficient to manually “Redeliver” any failed Webhooks that your App missed during its downtime (as described above). If it is important that your App never misses an event, you could build a recovery mechanism, using the GitHub API to fetch any data that they may have missed during your App’s downtime. Hope this helps! |
Beta Was this translation helpful? Give feedback.
👋 hi, @akmalick. Thanks for the question.
GitHub only communicates with your App via Webhooks, sending HTTP requests to a URL of your choice. As the owner of the App you can access a list of recent Webhook deliveries and see the payload we sent. If your Webhook URL does not respond with a 200, then the delive…