Start a run

Using Autopilot

Configure automatic code review for pushes and pull requests so V12 keeps watching important repositories.

Autopilot is V12’s continuous review workflow. Instead of creating each run by hand, add rules that review matching pushes or new pull requests automatically.

What Autopilot supports

Each Autopilot rule uses one of two behaviors:

  • Every push reviews every push to one branch you choose.
  • New pull requests reviews each pull request once, when it opens.

A repository can have more than one rule, so you can watch more than one of its branches.

Set up a repository

  1. Open Autopilot

    Go to the Autopilot page. In the last row of the table, click Add a repository. The row turns into a draft rule whose first field, choose a repository, is itself the search box.

  2. Choose a repository

    Type to narrow the list — each owner previews a few repositories and says how many more it holds — then pick one of the repositories available through your GitHub connection and app installation. The repository field also offers Manage repositories for GitHub access and Synchronize for refreshing the list.

  3. Choose a trigger

    Pick Every push or New pull requests.

  4. Qualify the trigger

    For Every push, type to filter the branch list and explicitly choose one branch. The Default tag marks the repository’s HEAD but doesn’t select it. The default is listed first, followed by conventional trunk branches (main, master, develop, development, dev, and trunk), then other branches alphabetically. Dependency-bot branches stay in the same list at the end. A branch claimed by another rule is marked In use and can’t be selected. There is no every-branch choice.

    For New pull requests, choose Members and collaborators or Anyone.

Choosing the branch or audience creates the rule. There is no separate Save step.

What you see on the Autopilot page

Each rule has its own row, and a repository can have more than one row. The table has four columns:

  • Repository links to the repository on GitHub.
  • Autopilot reviews reads as one condition: every push to main, or new pull requests from anyone. Use its trigger and qualifier controls to edit the rule. Switching a pull request rule to Every push asks for a branch before applying the change.
  • Last review links to the rule’s most recent run and shows its outcome and age. A rule that hasn’t fired shows whether it is waiting for a match or paused without any reviews.
  • Actions contains icon buttons to pause or resume the rule and to remove it.

Rules are ordered by repository, then trigger, scope, and rule age. Pausing or resuming a rule doesn’t move its row.

Pause, edit, or remove a rule

From a rule row you can:

  • edit the trigger, watched branch, or pull request audience inline,
  • use the pause or resume icon in Actions, or
  • use the remove icon in Actions to remove that rule.

Removing a rule stops future automated reviews for that rule. Reviews already produced remain available, and any other rules on the same repository keep running.

Manual GitHub trigger

If your GitHub integration is installed, an owner, member, or collaborator can also trigger a one-off pull request review by including @v12sec in a comment:

@v12sec pls audit

The full comment is passed to the run as context, so extra instructions travel with the trigger (for example, @v12sec please focus on the vault math).

When to use which mode

Review every push

Choose this when:

  • a branch is critical,
  • changes land directly on a long-lived branch, or
  • you want ongoing feedback without waiting for PR creation.

Review each new pull request once

Choose this when:

  • the repository has a high PR volume,
  • you want a lighter signal-to-cost ratio, or
  • you mainly want an initial security pass when a PR opens.

External contributor policy

For a pull request rule, choose Members and collaborators to review pull requests opened by repository owners, organization members, and collaborators.

Choose Anyone to also review pull requests opened by outside contributors. GitHub author association controls this audience.

Results

Autopilot runs still appear in the normal Runs workflow, so you can read findings, triage them, and share links exactly the same way as a manual run.

Type to search.