> ## Documentation Index
> Fetch the complete documentation index at: https://docs.scaling.cloud/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect GitHub

> Install the scaling.cloud GitHub App so investigations can correlate deploys, merges, and commits to incidents.

This guide installs the [scaling.cloud GitHub App](/integrations/github) for your organization so [investigations](/concepts/ai-investigations) can surface recent code changes as `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.

<Steps>
  <Step title="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.
  </Step>

  <Step title="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.
  </Step>

  <Step title="Map repositories to components">
    Investigations correlate a change to an incident by the [component](/concepts/components) it touched. Make sure each repository resolves to a component:

    * For a one-repo-per-service layout, add the repository name as an [alias](/concepts/components) 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.
  </Step>

  <Step title="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.
  </Step>
</Steps>

## Troubleshooting

| Symptom                              | Fix                                                                                                                  |
| ------------------------------------ | -------------------------------------------------------------------------------------------------------------------- |
| Connect button is disabled           | You're not an organization admin. Ask an admin to connect GitHub.                                                    |
| No `suspect_change` findings appear  | Confirm the incident's components have repository aliases, and that the change landed close to the incident's start. |
| "The GitHub App isn't available yet" | The integration isn't enabled for your workspace. Contact support.                                                   |

## Remove

Open **Settings → Integrations → GitHub** and click **Disconnect GitHub**. scaling.cloud stops reading changes immediately.