What this integration enables
- Repository context — agents can read
.sureops/services.yaml,catalog-info.yaml, andCODEOWNERSfiles to understand service ownership and relevant runbooks - Fix PRs — resolution specialist opens draft pull requests against your repository for code-change recommendations (requires a default repository configured)
- Deployment correlation — agents can correlate recent commits and PR merges with incident timing during diagnosis
- Change-tracking issues — sureops files GitHub Issues as change-tracking records for incidents (when GitHub is selected as your change tracker)
Prerequisites
- A GitHub organization where you have Owner or sufficient admin permissions to install a GitHub App
- The repositories you want sureops to access must be selected during the app installation flow
Setup
1
Install the GitHub App
In sureops, go to Settings → Integrations and click Connect next to GitHub.You will be redirected to GitHub to install the sureops GitHub App on your organization. Select which repositories sureops can access — you can grant access to all repositories or choose specific ones.
2
Select repositories
During the GitHub App installation, choose which repositories sureops can read. For fix PRs and change-tracking issues to work, include at least the repositories where your services’ source code lives.After installation, you’ll be redirected back to sureops with the connection confirmed.
3
Configure a default repository (optional)
If you want sureops to file change-tracking issues and fix PRs against a specific repository, set a Default Repository in the integration configuration field.Format:
owner/repo (for example, acme/incidents). If left blank, the GitHub integration works for read-only context but fix PRs will not be filed automatically.