GitHub
Connect GitHub to the AI agent: repositories, issues, pull requests, commits and Actions runs
Connect GitHub to the AI agent: repositories, issues, pull requests, commits and Actions runs. The agent finds PRs awaiting review and failing builds.
DocumentationWorkflow build.yml упал на шаге «Run tests», коммит a4f19c2.
- Из 14 прогонов за ночь красных 3 — все на одном и том же шаге
- Первый красный прогон пришёл сразу после мерджа PR #482
Скинуть лог упавшего джоба?
Integration scenarios
What is stuck without a review
The agent collects the open pull requests across your repositories and shows what has been waiting for review the longest and who is worth a nudge.
Digging into failing builds
The agent finds failed GitHub Actions runs and shows which commit and which step the build broke on.
Repository digest
The agent sends a daily digest: new PRs, closed issues and build status, on whatever schedule you agree with it.
Events straight into the team chat
The agent catches a push, a new issue or a review request over a webhook and posts it to the team chat right away instead of the next morning.
How to connect
Sign in with the right GitHub account
Open github.com under the account that already has access to the repositories you care about. The agent never sees more than this account does.
Check who installs apps in your organization
If the repositories belong to an organization, only an owner can install a GitHub App: a member only gets "Install and request", and the install waits as a pending request. Line up an owner first.
Start a SAML session for the organization
If the organization enforces SAML SSO, visit github.com/orgs/ORG/sso and start an active session before installing. Without it the organization is not even listed as an install target.
Choose which repositories the app gets
On the install screen pick "All repositories" or "Only select repositories" and tick the ones you need. Access is defined by the installation, with no tokens or scopes to issue; anything outside that list does not exist for the agent.
Know where to change access later
Personal account: Settings → Integrations → Applications → "Installed GitHub Apps" → "Configure". Organization: Settings → Third-party Access → "GitHub Apps" → "Configure". New repositories are added there too.
What the agent does in the first 10 minutes
- Collects open pull requests and issues across your repositories and shows what has been waiting for review the longest
- Finds failed GitHub Actions runs and points at the commit and the step where the build broke
- Sets up a daily repository digest — new PRs, closed issues, build status — you approve the time, then it runs on its own
FAQ
How do I connect GitHub?
By signing in through GitHub: press the connect button and approve the app installation — no keys to type in. In an organisation the owner installs the app, and with SAML SSO open a session at github.com/orgs/ORG/sso first, otherwise the organisation will not appear in the list.
What can the agent see in GitHub?
Only the repositories ticked during installation: their issues, pull requests, comments, commits and GitHub Actions runs.
How do I widen the access?
At installation you choose All repositories or Only select repositories. The list can be changed later through Configure on the app — the agent starts seeing the added repositories straight away.
What about events and limits?
The webhook delivers pushes, PRs, issues, reviews and completed workflows, so there is no need to poll the API. Requests themselves go out no faster than 10 per second to stay clear of GitHub rate limits.
