What our GitLab integration can do
- Export your incident follow-ups to GitLab
You can export your follow-ups to GitLab. We’ll sync the status of your tasks, so you can work in GitLab without worrying about updating statuses manually in incident.io!
You’ll see the option to export your follow-ups from the incident homepage:
- Link GitLab issues to your follow-ups.
You can copy the reference of issues you already have and linked them back to your incident.io follow-ups.
- Attach GitLab Merge Requests to incidents from Slack
You can attach GitLab MRs to your incident directly from the incident channel.
- Attach GitLab MRs to incidents from GitLab
You can also attach an MR by mentioning the incident number in the MR title or source branch.
Setting Up
Adding GitLab to incident.io is simple.
You’ll need a GitLab top-level group owner to perform some of these steps.
1. Create a Service Account user in GitLab
Follow GitLab’s guide to creating a service account.
We recommend using ‘incident.io’ for the name, since this will show up in the UI on issues and comments created by the integration.
Make sure the bot user has access to create and edit issues, and view and comment on merge requests in all relevant projects.
Reporter role to your incident.io service account user.
If connecting the GitLab integration for AI SRE you should instead assign the Developer role. This allows AI SRE to open Merge Requests when users request it.
2. Create a Personal Access Token
Follow GitLab’s guide here.
For scopes the integration requires the api scope.
After generating the token, make sure to copy the token value for the next step!
3. Connect the integration
Go to Settings → Integrations, click on GitLab, then Connect.
Paste in the access token created in step 2. and click Connect. That’s it
For GitLab users to connect with their incident.io accounts, their GitLab public email must:
- Match their incident.io user email
- Be visible on their GitLab profile
→ Next up
We recommend adding a Group Hook in GitLab, which allows us to sync changes in GitLab back to incident.io. Read our setup guide here.
If you run into any issues, get in touch
