suspect_change findings.
Prerequisites
- The Admin role in your scaling.cloud organization and in your GitHub organization.
- A plan that includes AI Investigations (Pro or Enterprise) to see findings on incidents.
1
Open the GitHub integration
In scaling.cloud, go to Settings → Integrations and open the GitHub card. If you are not an org admin, the connect button is disabled.
2
Install the GitHub App
Click Connect GitHub App. You’ll be redirected to GitHub to install the scaling.cloud app on your organization and choose which repositories it can see. Approve and you’ll return to scaling.cloud, where the card shows Connected with your account and installation.
3
Map repositories to components
Investigations correlate a change to an incident by the component it touched. Make sure each repository resolves to a component:
- For a one-repo-per-service layout, add the repository name as an alias of its component.
- For a monorepo, add path-scoped aliases (e.g.
acme/platform:services/payments) so changes map to the right component by path.
4
Verify on the next incident
On the next
critical incident whose affected components map to a repository with recent activity, open the Findings panel. A deploy or merge that landed shortly before the incident appears as a suspect_change finding with a link back to GitHub.