Autopilot
Rules that start runs on pushes, new pull requests or a daily or weekly schedule, how to ask for a review in a pull request comment, and what V12 posts on the pull request.
Autopilot starts runs for you. Each rule watches one repository and starts a run on every push to a branch, once for each new pull request, or daily or weekly. For a one-off review, ask from a pull request comment.
Before you start
- The Admin role. Only Admins can add, change, pause or remove rules, also over MCP; Members can see them. See Roles.
- The GitHub App. Autopilot works only on repositories V12 reads through the GitHub App, not on a public repository added without it. See Connect GitHub.
- Credits. A rule's runs are charged like any other run, and the organization's monthly limit still applies. A run that the balance or the limit cannot cover, counting a change review at its maximum, does not start; on a pull request, V12 then comments that the review "costs up to" its maximum. See What a run costs.
Add a rule
Open Autopilot and click Add a rule.
In Add a repository, pick the repository. A repository that already has rules shows On Autopilot; add another rule to it with Add a rule in its own menu.
Click choose a trigger and pick Every push, New pull requests, Daily or Weekly.
Fill in the trigger's field, described below; for Daily and Weekly, see Scheduled reviews. Choosing a push rule's branch or a pull request rule's audience saves it. To stop instead, click Discard (the × at the row's end).
Every push reviews every push to one branch, picked in choose a branch. The default branch is marked DEFAULT. A branch another push rule on the repository already watches shows In use.
New pull requests reviews each pull request once, when it opens, unless a skip rule matches. A repository can have one pull request rule. Choose the audience:
- trusted authors: pull requests from people who own the repository on GitHub, belong to the organization that owns it, or collaborate on it;
- anyone: forks and first-time contributors too.
The draft setting starts at drafts excluded, which reviews a draft pull request when it is marked ready. drafts included reviews drafts as they open. Change it before you choose the audience, or edit the rule afterwards.
Attach Steers
A new rule carries no Steers, and its row shows No Steers. Click Attach a Steer on the row and pick a Steer, or New Steer… to write one. A rule carries up to 5 Steers from anywhere in the organization. Each time it fires, it starts one run carrying all of them. Steers guide what the run looks for; they don't change what it reviews.
Pause, edit or remove a rule
Click a rule's row to change its trigger, branch, audience or draft setting, then press Enter or click Save rule (✓). Esc leaves it unchanged.
The Rule actions menu (…) on each row also has:
- Pause or Resume.
- Run now: starts the rule's run on the latest commit of its branch, without showing a price; on a Daily or Weekly rule it reviews the whole branch. Not on pull request rules; Members can use it too.
- Remove rule…: stops the rule. Runs it already started continue.
Under Repository, the same menu has Pause all rules (Resume all rules once all are paused), Open on GitHub and Remove from Autopilot….
Paused rules
A paused rule starts nothing and is listed under the Paused tab. Its row says why:
- Paused by owner: an Admin paused it. Click Resume to turn it back on.
- Paused: GitHub access lost: V12 can no longer read the repository. The rule resumes by itself when GitHub grants access again. Check GitHub access opens the GitHub section of Settings → Repositories.
Daily and Weekly rules can also pause themselves; see Scheduled reviews.
Ask from a pull request comment
No rule is needed. On a pull request in a repository with the GitHub App, write a new comment that mentions @v12sec, or the V12 app that comments on your pull requests:
@v12sec please check the new withdrawal limit- The commenter must be a trusted author, as defined under Add a rule.
- Only a new comment counts, not an edited one.
- The
@is required. In a comment of up to 8,192 characters, V12 ignores mentions inside quoted replies, code blocks and inline code, and an escaped\@v12sec; in a longer comment, any mention counts. - The run reviews the pull request's changes and reads your comment, so you can add instructions after the mention.
- Closed and merged pull requests are ignored. If a review of the pull request is already queued or running, including a rule's review with Steers, V12 replies with a link to it instead of starting another.
- Each request is a paid run.
What V12 posts on the pull request: see Pull request reviews.