> ## 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.

# GitHub

> Connect the scaling.cloud GitHub App so investigations can correlate your deploys, merges, and commits to incidents as suspect changes.

The GitHub integration is a [signal source](/concepts/signal-sources) for [AI investigations](/concepts/ai-investigations). Once connected, an investigation can correlate your recent code changes to an incident and surface the likely culprit as a `suspect_change` finding — *"deploy `abc123`, 8 minutes before the first alert, touched `payments/`."*

This is a **read** integration: scaling.cloud reads change events from GitHub to enrich investigations. It does not push GitHub alerts into scaling.cloud as incidents.

## What it does

* Receives deploy, pull-request, and commit events from your connected GitHub organization.
* Correlates each change to an incident by **time and the [component](/concepts/components)** it touched.
* Surfaces correlated changes as `suspect_change` findings on the incident, with a link to the deploy or PR.

## How changes map to components

A GitHub repository maps to a component through the catalog's [aliases](/concepts/components). A repository name is treated as an alias of the component that owns it, so changes to that repo are attributed to that component automatically.

For a **monorepo**, register path-scoped aliases (for example `acme/platform:apps/web` and `acme/platform:services/payments`) so one repository maps to different components by path. The most specific matching path wins, with the repository-level alias as a fallback.

## Connect

Connecting installs the scaling.cloud GitHub App for your organization. You need the **Admin** role in both scaling.cloud and GitHub.

<Card title="Connect GitHub" icon="github" href="/guides/connect-github">
  Step-by-step installation and verification.
</Card>

## Remove the integration

Open **Settings → Integrations → GitHub** and click **Disconnect GitHub**. scaling.cloud stops reading changes from your GitHub organization immediately. Existing findings on past incidents are unaffected.