Start and follow a run

Start a run on code or a change, approve its price, and follow it to the findings.

A run reviews code in your repositories, or one change. Every organization member can start and cancel runs, paid for with credit; see What a run costs.

Start a run

New run opens in the command menu. Open it with:

  • ⌘K (Ctrl+K on Windows and Linux), then New run….
  • New run on Runs, or on Findings when the switcher shows All repositories.
  • New run in a repository workspace's header, to start on that repository at the position on screen.
  • Run now on a repository's page, under its name, or in its Findings while nothing has been found at the position you're viewing. New run starts on that repository, at that position from Findings.
  • Run now in the organization's Findings while nothing has been found in any repository, or on Runs before the first run. New run asks which repository.
  • Run now on a Steer, which attaches it; see Run with a Steer.
  • Resume on a draft.

V12 can't run an archived repository, or one it can't reach on GitHub.

Review code or a change

New run asks one question at a time. Click an earlier answer to change it; when that clears later answers, Undo brings them back for 8 seconds. The search at the top also takes a pasted pull request number, commit SHA, branch name or GitHub link, under Jump to.

Which repository? Pick one, or type in Search, or paste a GitHub link. Paste a link to a repository outside the workspace and press Enter to add it.

What kind of review? Point in time: the code as it is on a branch or at a commit. A change: a pull request, a branch compared with the default branch, or a range of commits. A change needs the repository's history, so it waits until V12 has imported it.

For Point in time, answer Which branch? and Which commit? (the newest is tagged latest). In Which folders?, tick at least one folder or file: the run reads only what you tick, and nothing is ticked for you. Before V12 has imported the history, Use main as it is now (named after the default branch) reads that branch as the run starts; V12 imports the history when the run finishes.

For A change, answer Which change?: a Pull request (GitHub repositories only), a Branch since it left the default branch, a Commit range on a branch from one commit (From) to another (To), or what's new on the default branch Since V12's last review. For a pull request or a branch, How much of it? offers the whole change or, when V12 reviewed an earlier version, only what's new since that review. Read the diff shows what will be reviewed. A change of more than 3,000 files can't be reviewed; New run says "Over 3,000 changed files".

What should V12 look for? (optional): name a risk, a file or a kind of bug. Type @ to reference a file, commit, pull request, finding, document or saved Steer; a run carries up to 5 saved Steers. Drop or paste a PDF, Markdown, text, JSON, DOCX or CSV file on the box. A document V12 can't read, such as a scanned PDF with no text, says why; remove it to continue.

Save as Steer turns your words into a Steer and attaches it in their place.

Add another repository, under Which folders?, adds another repository to a code review, with its own branch, commit and folders, up to 9 repositories.

Approve the price

Your run shows the Estimate, the Credit after the run and, until the run can start, what's missing. For a change, the Estimate is the most the review can cost, such as Up to $9.60; Credit after, at least is what's left if it costs that much, and a note gives the range you pay, such as "You pay the review's metered model usage: at least $0.50, at most $9.60." Review run (⌘Enter or Ctrl+Enter) shows Review your run; there, Start run starts the run and opens its page, and Save draft keeps the plan as a draft.

For a code review, Detect and triage only under Which folders? skips proofs of concept and fixes and lowers the Estimate; the run page shows Prove and fix as Skipped.

Start run and Save draft wait for the price, and stay unavailable while a document is uploading or failed, a repository in the run has nothing ticked, or a repository in the run is inaccessible.

For lack of credit, V12 refuses the start with "Insufficient credit balance." and Add credit, or "Monthly spending limit reached." and Raise the limit. Both link to Settings → Billing.

Esc steps back one level at a time: it clears the search, leaves the diff or Review your run, keeps a reopened answer, and then leaves New run; a click outside leaves directly. If you've changed an answer, leaving asks Discard this run? first. Leaving never discards a saved draft.

Drafts

A draft is not started and not charged. Only you see your drafts, marked Draft in Runs. Resume reopens New run on Review your run with the saved answers; Start run waits for a fresh price. A draft saved with nothing ticked asks Which folders? again. Save draft there replaces the draft. Discard removes it. Only whoever saved it, or an Admin, can do either.

Follow a run

The run page and Runs show each run's status: Queued, its current stage, then Complete, Failed or Cancelled.

The run page's progress rail shows the stages:

  • Code review: Queue, Compile, Scan, Triage, Prove and fix, Report, Inbox.
  • Change: Queue, Compile, Review changes, Triage, Inbox.

The header links every Steer the run carried. Below, each Steer shows its frozen Markdown source in a card, followed by the run's own words under Steering. A card shows its line count. Its chevron collapses the card; chevrons beside headings fold individual sections while keeping the original line numbers. Copy copies the entire stored document, even when it is folded.

With more than two instruction cards, only the first starts open. Collapse all puts the cards away without forgetting section folds; Expand all opens every card and section.

Scope lists the files captured for the run, not a fresh listing of the repository. For larger scopes, filter by Source, Folder or Language, or use Search files. Choose several values within a filter to include any of them; different filters narrow one another. Sort by Lines or Path, and use Show 25 more to continue beyond the first twelve files. Clear filters restores the whole scope.

A missing line count appears as a dash; partial totals say "known lines". A change's excluded files stay visible as Not reviewed. Repository and commit links identify each source, and Diff opens the comparison when one is available.

Cancel stops a queued or working run. A working change review stops at its next checkpoint, showing Cancelling until then. A code review that fails, or is cancelled before it started, is refunded in full; a change review that fails or is cancelled costs nothing.

On a failed run, whoever started it, or an Admin, sees Retry, which starts it again as a new run.

After the run

A completed run lists its findings under Findings and sends them to the inbox.

  • If the page shows Import findings, click it. If that fails, Retry appears.
  • If the run's repository isn't in the workspace, its findings wait. Add it with Add repository on the run page or its row in Runs, then click Import findings. If you can't add it, an Admin gets Manage GitHub access ↗ and a Member Review repositories, both opening the GitHub section of Settings → Repositories.
  • Export findings that did not reach the inbox.
  • Share publishes a read-only report and makes guest links to the run's findings for people outside your organization.
  • A run started by an Autopilot pull request rule or an @v12sec comment shows Review: where V12's review on the pull request stands. See Pull request reviews.

On this page