Configure review automation
Set the organization's review behavior, then adjust repository settings where a repository needs different behavior.

Change organization settings#
- Open Settings → Review policy → Automation.
- Choose when Proofline should review.
- Decide whether to review draft pull requests.
- Set the quiet period after pushes if needed, and save your changes.
The quiet period lets closely spaced pushes settle before a review starts.
Review without posting to GitHub#
Shadow mode keeps automatic review results in the console while you assess what they would publish. Run automatic reviews without posting to GitHub.
Review a share of pull requests#
Set a sampling percentage in the organization or override it under a repository's Review scope. Choose which share of pull requests gets automatic reviews.
Read repository guidelines#
Read repository guideline files makes the repository's guidance available to the reviewer. Include repository guidelines in code reviews.
Change repository settings#
Open Repositories, select a repository, then open Settings → Automation to choose whether to review, whether shadow mode applies and how to review agent-authored pull requests. Its Settings → Code review page sets when to review drafts, strictness, the inline comment limit, the code checks, finding comments and which environments to review. Select Save review settings after changing a value.
Use Review scope to filter pull requests, authors, bots, and files. These groups remain visible while you edit. To leave generated output out, mark generated files and enable the exclusion.
The Settings → Review preferences page contains proposals drafted from GitHub replies, repeated decisions and review history. Approve a proposal there to apply it to later reviews; see Approve learned review preferences.
Under Trigger labels, choose existing GitHub labels and select Save trigger labels. Adding a selected label requests a review of the current head only when the person adding it has repository write access.
Suggest labels and reviewers#
Use Settings → Automation in the repository to configure path labels and reviewer suggestions. Suggest GitHub labels and reviewers from changed paths.
Configure code checks and comments#
The organization's Code review settings control which checks run and how findings appear on GitHub. Choose which code checks and comments appear in reviews.
Require a completed review before merging#
Open the repository's Settings → Merge gate page. Select Enable merge gate, choose the blocking severity, and confirm the policy. A code-only repository can enable the gate without a linked environment.
Add Proofline gate as a required check in GitHub's branch protection or ruleset. Enabling the policy does not change GitHub's rules.
An incomplete review or an open supported finding at the selected severity blocks the gate. If the review checked an environment, incomplete environment evidence or a blocked required check also blocks it. A review that checked no environment is decided on its code findings alone.
The policy applies to new pull request heads. Existing heads keep their recorded policy. Use View history to inspect recorded decisions.
Choose review coverage#
Each environment's review focus is on its Setup page. After you write the focus, select Recommend from focus under Risk domains. Review the recommended domain choices before saving.
You can edit domain choices while the recommendation runs. If you do, the result preserves your edits until you select Apply recommendation.
Resolve a save conflict#
If another session changes the settings, Proofline keeps your draft and asks you to reload the current settings. Review the current values before saving again.
Deployment protection also needs an environment and a supported delivery setup. See Configure deployment protection.