Scheduled reviews
Daily and Weekly Autopilot rules that review a branch at a set time, either its new changes or the whole branch.
A Daily or Weekly Autopilot rule reviews one branch at a time you set, instead of on every push. Use one to keep a branch reviewed without starting a run for each push.
Before you start
- The Admin role. Only Admins can add, change, pause or remove rules; Members can see them and use Run now. See Roles.
- The GitHub App. As for every rule, the repository must be one V12 reads through the GitHub App. See Before you start.
Add a scheduled rule
Open Autopilot, click Add a rule and pick the repository in Add a repository.
Click choose a trigger and pick Daily or Weekly.
For Weekly, pick the day in choose a day. Set the time, then pick the branch in choose a branch.
Check the last word of the rule, which sets what each review covers: new changes, the default, or whole branch. Both are described below.
Click Save rule (✓).
The row then reads, for example, Daily at 09:00 on main · new changes. A branch can have one Daily and one Weekly rule.
Times
You set the time in your time zone, and V12 keeps it as a fixed time in UTC. While you add or edit the rule, hover the time field to see it, for example Runs at 07:00 UTC every day. After a daylight-saving change, reviews run an hour earlier or later in your time zone; the row always shows the next review in your time zone.
New changes or the whole branch
- new changes: a change review of what landed on the branch since the last review, priced like any change by its changed files and lines. The first review covers what landed since you saved the rule, switched it to new changes or moved it to another branch. What a failed or cancelled run missed is reviewed by the next review, unless you retried it and the retry has not failed or been cancelled. After a force-push, the next review covers the branch from where its old and new history meet, so rewritten commits are reviewed again.
- whole branch: every file of the branch, every time, at the price of a full review, even when nothing changed.
To switch, click the rule's row, pick the other word, and click Save rule (✓). See What a run costs.
When nothing runs
A new-changes review with nothing to review starts no run and costs nothing. The rule's row says why, with how long ago it checked; hover it for details:
- Nothing new: nothing landed on the branch since the last review.
- Nothing to review: the changes touched no file V12 reviews.
- Too large to review: over 300 files changed. The next review starts from here.
- History rewritten: GitHub can no longer compare the branch with the last reviewed commit, as when the branch was deleted and recreated. The next review starts from here.
Run now
Run now, in the rule's Rule actions menu (…), starts a run on the latest commit of the branch right away, without showing a price. On a scheduled rule it always reviews the whole branch, at the price of a full review; on a new changes rule the item carries the hint Whole branch. The schedule carries on unchanged.
Paused rules
A paused rule starts nothing. Besides the reasons in Paused rules, a scheduled rule pauses itself when its review cannot start:
- Paused: branch unavailable: the branch was deleted. Click Pick another branch.
- Paused: out of credit: the balance or the monthly limit could not cover the run. Click View billing, then Resume the rule.
- Paused: no workspace owner: the workspace's GitHub connection can no longer start runs. Click Reconnect GitHub; the rule resumes by itself once it works.
When you resume a rule whose review time passed while it was paused, one review starts at once and covers everything since the last one. Missed reviews are not repeated.