GitHub integration
Install the Angada GitHub App, control which repos it can see, and recover access.
The GitHub integration is how Angada sees your pull requests. Everything else — reviews, Slack cards, wikis, digests — reads from the repository access you grant here.
What the App can do
The Angada GitHub App reads activity in the repositories you grant it: pull requests, pushes, reviews, and CI status. That feed drives your living PR cards, the AI Wiki, and dashboard views.
When AI Review is enabled for your Workspace, review operations require these GitHub App permissions:
| Permission | Access |
|---|---|
| Pull requests | Write |
| Checks | Write |
| Issues | Write |
The App also needs the issue_comment, check_run, and pull_request_review_thread webhook events. These permissions and events are required for AI Review; an existing installation may still be waiting for approval to add them.
You choose which repositories the App can access, and you can change or revoke that access at any time from GitHub's side.
For the customer-facing data boundary and Slack access details, see Privacy & security.
GitHub's install screen with repository access selection.
Install the App
- On the Connect your code step of onboarding, select Connect GitHub.
- You're taken to GitHub's own installation screen. Choose All repositories or Only select repositories, then pick which ones.
- Approve the install. You're returned to Angada, where the step now shows GitHub connected.
Required role: you need permission to install GitHub Apps on the organization (an organization owner, or a member with app-installation rights).
What Angada sees afterward
Your connected repos mirror the App's installation exactly — nothing is curated inside Angada. If a repo is in the install, it's connected; if it isn't, it won't appear no matter what you do in Angada's settings.
To add or remove a repo, change the App's repository access in your GitHub installation settings, then let Angada re-sync. Syncs run automatically after access changes, and you can trigger a re-sync from the Slack connection screen. See Why don't I see a repo in Angada?
Approve new permissions
GitHub keeps an existing installation's current permissions until an organization admin approves a request for additional permissions. While the review permissions are pending, GitHub monitoring can continue with the permissions already granted, but AI Review cannot proceed.
An organization admin can review and approve the request in GitHub's installation settings. For details, see GitHub's guide to approving updated permissions for a GitHub App.
Where results appear
- On the pull request — the Angada check run, and review comments when AI Review is enabled. See Understand a review.
- In Angada — the triage dashboard, findings, and wiki generation for the same repos.
- In Slack — living cards and digests, routed by your channel routing.
Connection states and recovery
A GitHub connection is active, suspended, or revoked:
- Suspended — the installation was paused from GitHub's side. Angada stops receiving activity until it's resumed.
- Revoked — the App was uninstalled. Angada stops entirely until it's reinstalled.
Disconnecting on Angada's side pauses activity without erasing your dependent setup — routes, digests, and history stay intact. Reconnecting can resume the same GitHub installation or swap to a different one.
If PRs stop updating, check the installation state on GitHub first: an expired or removed installation is the most common cause, and re-approving the App restores everything without reconfiguration.