Auto-Update PRs
The bot can bring open PRs up to date with their base branch — by merging or rebasing the new base into the PR head. This saves PR authors from manually updating branches every time someone else lands a change.
The feature is off by default and must be enabled per repo in the dashboard.
Enabling it
Section titled “Enabling it”Open the repository’s settings page in the dashboard and find Auto-update PRs. Pick a Mode:
| Mode | Behavior |
|---|---|
| Off (default) | Disabled — the bot does nothing. |
| Automatic | Every push to the base branch triggers an update across all open PRs that target it. |
| Manual | Updates only run when triggered from the dashboard’s Pull Requests page. The bot does nothing on push. |
When Mode is Automatic or Manual, two more settings appear:
Conflict handling
| Option | Behavior |
|---|---|
| Only when clean | Updates the PR if the merge or rebase is clean. On conflict, posts one comment asking for a manual update and stops. The coding agent is not invoked. |
| Resolve conflicts with agent | Updates the PR and runs the conflict-resolution loop on the coding agent if needed. |
Strategy — pick Merge or Rebase as the update method.
Per-PR escape hatch
Section titled “Per-PR escape hatch”Add the no-auto-update label to any PR you don’t want the bot to touch.
PRs the bot skips
Section titled “PRs the bot skips”Regardless of mode, the bot skips:
- Draft PRs
- PRs from forks (the bot doesn’t have write access to fork head branches)
- PRs the bot itself opened
- PRs already up to date with the base branch
- PRs labeled
no-auto-update
What you’ll see on the PR
Section titled “What you’ll see on the PR”| Conflict handling and outcome | Comment posted |
|---|---|
| Only when clean, clean update | None. |
| Only when clean, conflict detected | ”I tried to auto-update … please update manually.” |
| Resolve conflicts with agent, any outcome | One progress comment with steps and a final success or give-up summary. |
| PR skipped (draft, fork, up to date, etc.) | None. |