GitHub
The GitHub App is what powers release attribution. Without it, we see span-level release IDs but can't walk the commit graph to tell you which PR introduced a regression.
What the App needs
The GreenSlope GitHub App requests read-only access to:
- Metadata — repo name, default branch.
- Contents — read only. Used to resolve commit ranges between two release IDs.
- Pull requests — read only. Used to name the PR that introduced a change.
- Commit statuses — read only. Used to show deploy state on the Doctor page.
We do not request:
- Write access to any repo.
- Access to secrets or Actions workflow runs.
- Access to Issues or Discussions.
See Security and data handling for the full classification of what we retain and for how long.
Install
- In the dashboard, go to Settings → Integrations → GitHub.
- Click Install GitHub App. You'll be redirected to GitHub.
- Pick All repositories or a subset. You can narrow or widen this later from GitHub's App settings — GreenSlope respects the scope without a reinstall.
That's it. Release attribution lights up on the next deploy.
Multi-repo services
If a single logical service spans multiple repos (frontend + API in separate repos, shared release process), add both repos to the same service on the integration settings page. Release attribution walks commit graphs per repo and merges the results.
GitHub Enterprise
GitHub Enterprise Server (self-hosted) and GitHub Enterprise Cloud are both supported. For Enterprise Server, you'll need to provide the base URL of your Enterprise instance during install. See the Security page for network-allowlist details.
Uninstall
From GitHub Settings → Applications → GreenSlope → Uninstall, or from the GreenSlope dashboard. Uninstalling stops the commit-graph lookup; existing alerts still reference the release IDs but the PR links go stale.
Related