Full control over your code review

Choose when a review runs

Reviews can cover pull requests, deployments, or both. You choose whether draft pull requests get a review right away or once they are marked ready.

A quiet period lets a burst of pushes settle before a review starts. To start one by hand, use the console, a pull request command, or a trigger label.

You assign seats to the developers whose pull requests get automatic reviews. See how to configure review automation.

Limit what it reads

Review scope filters pull requests by base branch, label, author, bot, and path, and can leave out generated files.

You pick the repositories the GitHub App can access and the infrastructure each environment connects. Evidence connections are read-only. A Cloud Build deployment gate also approves or rejects the builds it holds. See security and data access.

Choose what it may block

By default, reviews are advisory. The Proofline check stays neutral and never blocks a merge on its own.

To enforce a policy, enable the merge gate and choose its blocking severity. Then add the Proofline gate check as required in GitHub. A deployment gate can also hold a GitHub Actions or Cloud Build deployment.

Steer it from the pull request

Mention Proofline in a pull request comment to run one of its 11 commands, including status and help. Commands can start or stop a review, dismiss or confirm a finding, accept a risk, or ignore a path or risk domain.

Before it interprets a request, Proofline checks that the commenter has write access in GitHub. Comments from anyone else do not steer the review.

Cap spend and retention

Monthly credit limits can cover the organization or one repository. You can also cap each review and give each developer a monthly allowance.

Once a monthly limit is reached, new reviews in its scope do not start. Each one shows as incomplete and names the limit that stopped it.

Model transcripts can contain source code. Proofline keeps them for 30 days by default, and an administrator can shorten that to zero days through the API.

Custom roles decide who can change each setting, and you grant them to GitHub people or teams.

Questions

Can Proofline block a merge?

Yes, if you enable the merge gate and make the Proofline gate check required in GitHub. Reviews are advisory by default.

Who can run Proofline commands from a pull request comment?

Only people with write or admin access to the repository in GitHub can steer a review with a comment. Proofline checks that access before it interprets the comment.

How do I limit AI code review costs?

In Proofline, set monthly credit limits for the organization or a repository, a credit limit for each review, and a monthly allowance for each developer.