Keep a repository audit current with pushes to a branch

An audit cadence starts a new code-only audit of a repository after pushes to one branch. Each refresh audits the newest commit pushed and compares its findings with the audit before it, so a team that pushes to a working branch directly keeps its audit current. You set up and change a cadence in chat, and the repository's Audits list shows it with its newest firings. Proofline sends no message when a refresh is refused, so read the cadence to learn what happened.

Before you start#

  • You administer the organization. Only its administrators can create, change or delete a cadence.
  • Audits are on for the organization: its review settings show Maximum credits per repository audit above zero. While audits are off, a cadence cannot be created or turned on, and an existing one starts nothing.
  • The repository has a code-only audit that ended completed or incomplete. A cadence's first refresh compares with this baseline. A failed, stopped or still-running audit cannot be the baseline. Start one from the repository's Audits list if it has none.

Enable a cadence#

Ask your connected agent:

For this repository, propose an audit cadence on the main branch with a 60-minute refresh interval. Use the newest code-only audit that ended completed or incomplete as its baseline, with the per-refresh and monthly credits I specify. Show any existing cadence for that branch first.

Check the repository, branch, interval, baseline audit and both credit limits before applying. Name the branch without refs/heads/; a name with slashes, such as release/2026-11, is fine. A repository has one cadence per branch, so change the existing cadence instead of adding a second.

An incomplete baseline is accepted because an audit of a repository whose areas import each other widely can end incomplete however many credits it has. The first refresh marks each of the baseline's findings it did not examine as not examined, as a refresh you start from an incomplete audit's report does.

The two limits work together:

  • Per-refresh credits cap each refresh, as the cap does for an audit you start from the Audits list. They cannot exceed the organization's maximum credits per repository audit.
  • Monthly credits cap what the cadence's refreshes may be given together in one calendar month, counted in UTC. Each refresh counts its full per-refresh cap, even when it spends less. The monthly limit is at least the per-refresh limit.

What starts a refresh#

Proofline checks the branch every 15 minutes. By default, each check can start a refresh. Choose 60 minutes to wait an hour after creation or the last firing. At the first eligible check, Proofline audits the newest commit pushed. A quiet branch spends nothing. Pushes during a running audit wait until it ends and the interval has elapsed. Pushes to other branches start nothing, and a deleted branch starts nothing until it is pushed again.

Each refresh is an ordinary code-only audit and appears in the repository's Audits list. It runs under the authority of the administrator who last saved the cadence.

A refresh a person starts with Refresh on the report of the cadence's newest audit, at the cadence's branch, counts as the cadence's. Newer pushes wait while it runs, and the cadence's next refresh compares with it, so its findings carry forward. A refresh of an older audit or at another branch does not count, and neither does a second refresh of the same audit. A refresh that is stopped or fails stops counting, so the cadence audits that commit itself.

Read a cadence and its newest firing#

Each time Proofline acts on a new commit, it records a firing: either a refresh it started or a refusal. Ask your connected agent:

Read our configuration and show the audit cadence for the main branch of this repository, with its newest firings.

The configuration read lists each cadence with its refresh interval, the newest commit pushed and when, the credits this month's refreshes were given, the administrator who last saved it, and its 10 newest firings, newest first.

Each firing names the commit it captured and when that commit was pushed, the audit it compared with, and its outcome. A firing that started a refresh names it, with the refresh's state, how many of its areas it completed and when it ended. A firing that found the commit already audited names that audit. The gap between the push and the firing shows how long the commit waited.

Respond to a refused firing#

A refused firing spends nothing and records a reason. Proofline does not try that commit again: the cadence fires next after another push to the branch. Fix the cause before that push.

  • UNAUTHORIZED: the administrator who last saved the cadence no longer administers the organization. An administrator saves the cadence again with its current limits, and refreshes then run under their authority.
  • MONTHLY_LIMIT: one more refresh would take this month's refreshes past the monthly credits. The firing's detail says how many credits this month's refreshes were given. Raise the monthly credits, lower the per-refresh credits, or wait for the next UTC month.
  • UNFUNDED: the organization's credits cannot pay for the refresh. Buy credits or turn on automatic top-up under Settings → Billing.
  • SPEND_LIMIT: a spend limit that stops new reviews has been reached, and the detail names it. Raise that limit under Spend limits, or wait for the next month.
  • OVER_CEILING: the per-refresh credits now exceed the organization's maximum credits per repository audit, or audits were turned off. Lower the per-refresh credits to within the maximum. While audits are off, the cadence cannot start a refresh.
  • ALREADY_AUDITED: an audit the cadence counts as its own already reads the commit, such as a refresh a person started at it. The firing names that audit, and the repository's Audits list links it as Already audited. Nothing needs fixing.
  • NOT_ADMITTED: Proofline refused to start the audit for another reason, which the detail states.

Change or turn off a cadence#

Ask your connected agent:

Propose changing the audit cadence on the main branch of this repository to the per-refresh and monthly credits I specify, and keep it enabled.

You can switch between 15 and 60 minutes. If you omit the interval, the cadence keeps its current interval. A change replaces both limits and whether the cadence fires, so state all three. A change that does not say the cadence stays off turns it back on. The repository, branch and baseline cannot change; to follow another branch, delete the cadence and create a new one. Saving a change makes you the administrator its later refreshes run under.

To pause a cadence while keeping its limits, propose disabling it. A disabled cadence starts nothing, but Proofline still records pushes to its branch, so once it is enabled again the next eligible check audits the newest commit.

To stop it for good, propose deleting it. A deleted cadence starts nothing and leaves the configuration read along with its firings. The audits it started stay in the repository's Audits list, and the branch can take a new cadence. A refresh already running finishes either way.

The organization's audit log records each creation, change and deletion with the settings before and after.

Search help

Tab to a result. Enter to open. Escape to close.