Skip to main content
The GitLab 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 merge requests that landed just before it. Rootly will automatically add the following GitLab events as pulses:
  • Push to any repositories
  • Merged merge requests
  • More to come…

​
How it works

Once the GitLab integration is connected, Rootly receives webhook events from your tracked repositories and records them as pulses on the incident timeline and service activity feed. Push events, merged merge requests, and deployment events each produce a pulse with labels and refs identifying the repository, branch, and commit. You can limit tracking to specific repositories in the integration settings to reduce noise. Beyond pulses, the GitLab integration also lets you create and update GitLab issues from incident and action item workflows, fetch recent commits during an incident, and enrich GitLab merge request links pasted into incident Slack channels with live status cards.

​
Getting the most out of GitLab pulses

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