GitHub
GitHub is where your code lives, and it's how Leroy ships. Connect it once with a GitHub App and Leroy can read your repositories and open pull requests for the work it does. This is the one integration Leroy effectively requires — every other source of work eventually lands as a PR in GitHub.
01 What it does
Leroy connects to GitHub as a GitHub App — a scoped, revocable install you grant on the repos you choose, not a personal access token. Once installed, Leroy can:
- Read your repositories — the code it needs to understand a change and write it correctly.
- Open pull requests on a branch — every change Leroy makes ships as a PR you can review, comment on, and merge like any other.
- Respond to PR review comments — leave feedback on the PR and Leroy can revise the work in place.
Branch protection is respected
Leroy works on branches and opens pull requests — it does not push to your default branch. If you have branch protection or a no-push-to-main rule, Leroy follows it: changes go through a PR and merge only when your rules (and your policy gates) say they can. We recommend turning on branch protection for your protected branches regardless.
02 Connect it
You connect GitHub from the Integrationsscreen in the Leroy app. The exact steps live there because GitHub's install flow can change, but the shape is always the same:
- Open Integrations → GitHub in the Leroy app and start the connect flow.
- Install the Leroy GitHub App on your organization (or personal account). GitHub walks you through the permission and repository prompts.
- Choose which repositories Leroy can access — all of them, or a hand-picked set. You can change this later from GitHub.
- Confirmand you'll land back in Leroy with GitHub connected.
03 What it unlocks
With GitHub connected, the full loop works:
- Work becomes pull requests. Whether a request comes from Sentry, Linear, Slack, or the app, the result is a reviewable PR on a branch.
- Review where you already work. Read the diff, leave comments, and merge from GitHub — or from Leroy. Comments flow back so Leroy can revise.
- Oversight you configure. Your policy gates decide whether Leroy merges on its own or waits for your approval, per repo.