Your first review

From Audits → New audit, choose a repository and a branch, and start it.

What happens while it runs

The review is queued and picked up by a worker. You can watch it move through its stages on the audit page: resolving the branch to a commit, fetching the snapshot, detecting which languages are present, running the analysis tools, and assembling the results.

Reviews run one at a time per workspace, up to three at once. If you start more, you are told to wait rather than silently queued behind a wall.

Why it reviews a commit, not a branch

Monterva resolves your branch to a specific commit and reviews that. If the branch moves while the review is running, the report still describes the commit it actually read.

This matters when you check a finding: the file and line number in the report refer to a commit you can check out, not to whatever the branch happened to be later.

Re-running after a fix

Once you have fixed something, re-scan the same repository. Monterva compares the new results against the previous review by matching each finding's fingerprint, not by counting them — so fixing one issue while introducing another shows as one resolved and one introduced, rather than as no change.

A re-scan is a full review and counts the same as any other.

If it fails

Some failures are worth retrying and are retried automatically: a rate limit, a dropped connection. Others are not, because a second attempt produces the same answer three minutes later — a deleted branch, revoked access, or an archive we refused to unpack.

Either way the audit page tells you what happened in plain language. If it is something only you can fix, it says so rather than retrying quietly.