GitHub
Connect the Nested GitHub App, then start agent tasks from pull requests, reviews, comments, pushes, and CI with automations or raw repository bindings.
Nested listens to GitHub through the Nested GitHub App. Most people start work from GitHub with a GitHub trigger in Automations, which turns GitHub’s many event types into plain presets. Raw repository bindings remain for agent-level setups.
Before you start#
- Open Automations and use the Integrations card: Connect your GitHub identity, then Add organization to install the Nested GitHub App on an organization you can see.
- The GitHub connector on the Connectors page is a separate thing: agents use it to work with repositories, for example in a repository workspace. Automations do not need it.
Start work with an automation#
- Create an automation and add a GitHub trigger.
- Pick the Organization and Repository.
- Under When, select one or more presets (see the table).
- Optional: add Mentions, GitHub logins without
@or[bot]. The run then starts only when one of them is @mentioned, requested as a reviewer, or assigned. - Optional: set Acknowledge comments to a reaction Nested adds right away to a pull request comment that starts a run.
- Optional: under When it finishes, turn on Comment on the pull request.
| Preset | Fires when |
|---|---|
| Pull request opened | A pull request is opened or marked ready for review. |
| Pull request updated | New commits land on an open pull request. |
| Review requested | Someone is requested as a reviewer or assigned. With Mentions set, only when one of those logins is requested or assigned. |
| Pull request merged | A pull request is merged. Closing a pull request without merging does not fire it. |
| Push to a branch | Someone pushes to a branch. |
| Comment on a pull request | A new comment on a pull request or in a review thread. Comments on plain issues do not fire it. |
| Review submitted | A pull request review is submitted. |
| Review thread | Someone comments on a line in a review. |
| CI finished | A check suite or workflow run completes, whatever its conclusion. |
| Workflow run finished | A GitHub Actions workflow run completes, whatever its conclusion. |
| Issue opened | A new issue is opened. |
| Label added | A label is added to a pull request. |
The webhook JSON is appended to the agent’s instructions, so the agent sees the pull request, comment, or run that started it.
Raw repository bindings#
From an agent’s settings → Automations → GitHub, select Add binding and walk the steps: Organization, Repository (or all repositories in the organization), Events — raw GitHub events such as Push, Pull request, Issues, Issue comment, Release, Pull request review, Review comment, Check suite, and Workflow run — optional Only these changes (actions such as opened, synchronize), optional Mentions / special users, and the Task template. Repository-level bindings win over organization-level ones when both match. Remove a binding when the repository should stop creating tasks.
Example#
Create an automation on your review agent: Pull request opened and Comment on a pull request on acme/app, Mentions nested-bot, Acknowledge comments with 👀, and Comment on the pull request on finish. When someone writes “@nested-bot please review”, the comment gets 👀, a task starts, and the agent comments back when it is done.
Questions
- Do I need the GitHub connector for GitHub automations?
- No. Automations use the Nested GitHub App from the Integrations card. The GitHub connector is for agents that work with repositories on your behalf.
- How do I stop every comment from starting a task?
- Add Mentions. The automation then runs only when one of those logins is @mentioned, requested as a reviewer, or assigned.