Skip to main content
The GitHub integration records repository activity as pulses in Rootly, giving responders a timeline of recent code changes alongside their incidents. When something breaks, pulses help you correlate the incident with the pushes and pull requests that landed just before it. Rootly will automatically add the following GitHub events as pulses:
  • Push to any repositories
  • Merged pull requests
  • More to come…

​
How it works

Once the GitHub integration is connected, Rootly receives push, pull request, and issue events from your repositories and surfaces them as pulses on the incident timeline and service activity feed. No extra configuration is needed for individual events — activity is captured automatically as it happens. Beyond pulses, the GitHub integration also lets you create and update GitHub issues from incident workflows, fetch recent commits across repositories during an incident, and automatically enrich GitHub pull request links shared in incident Slack channels with live status updates.

​
Getting the most out of GitHub pulses

  • Use pulses during triage to answer “what changed?” — a deploy or merge shortly before an incident is often the fastest lead.
  • Pair the integration with workflows to automate issue creation and keep GitHub in sync as incidents progress.
Ready to configure the GitHub integration? See GitHub integration setup.

Pulses

Where GitHub push and merge events appear as change events on incident timelines.

Services

Link services to specific GitHub repositories so pulses land on the right incident context.

GitHub Integration Setup

Full installation guide, permissions, and workflow actions.