GitHub Deploys
Connect GitHub and every deploy becomes visible where you debug: dashed markers on your monitors' response-time charts, and a "deploys before this incident" card on every incident that follows a recent deploy.
Connecting
- Open Integrations in your dashboard
- Click Connect GitHub and choose which account and repositories the app may see
- Back in Sentinel, link each repository to the monitor it deploys
A repository can feed several monitors, and a monitor can listen to several repositories. Each link has two switches: Mark deploys and Pause during deploys.
Privacy by design
The app only consumes webhooks GitHub sends it. It holds no API credentials, makes no API calls, and cannot read your code, issues, or anything else in your account. Its permissions are read-only metadata about pushes and deployments, and nothing more.
Deploy markers
A marker is recorded when a push lands on the repository's default branch, or when a GitHub Deployment is created. Markers are drawn at the start of a deploy: the dashed line on the chart is the moment the push or deployment happened, and the deploys behind the lines are listed under the chart. When a deployment later reports failure, its marker turns red.
On incident pages, any deploy from a linked repository in the hour before the incident opened is cited next to the root cause, timed against the incident start: the first question of every outage, answered before it is asked.
Pausing during deploys
With Pause during deploys enabled, the monitor pauses the moment a GitHub Deployment is created and resumes when the deployment reports success or failure. If a deployment never reports back, a failsafe resumes the monitor after 20 minutes, so a hung deploy can never silence monitoring for good. Monitors you paused by hand are never touched.
- Pauses require GitHub Deployments. They trigger on Deployment objects, created by GitHub Actions environments, Vercel, Railway, and most CD platforms.
- Plain pushes never pause. A push has no duration, so it only draws a marker.
- If your CI deploys without creating Deployments, you can still pause explicitly from your pipeline: see CI/CD & Pausing Monitors.
Disconnecting
Disconnect from the Integrations page, or uninstall the app from your GitHub settings; either way markers and pauses stop immediately. Removing a repository from the app's access on GitHub also removes its links in Sentinel.