Make a pull request check advisory or blocking
Choose how the check should conclude in Proofline, then configure the matching GitHub branch rule if the result must block merging.
Match the mode to the GitHub branch rule#
An Advisory check reports whether its requirement is met. Its Check always concludes neutral, so it never blocks a merge.
A Blocking check succeeds when its rule is met and fails when it is not. It needs action when Proofline could not read what the rule needs, such as a title or label set that GitHub did not send, or a description it could not read at the reviewed commit. The Check names the cause. To block merges, add its Check as a required status check in the repository's GitHub rules. Proofline does not change GitHub rules.
A blocking coverage check succeeds when its requirements are met, fails when they are not, and needs action when coverage is inconclusive. It is skipped when there are no changed executable lines.
In either mode, the separate Proofline check turns green when the advisory review finishes. It also turns green when a partial code review returns findings and all enabled environment checks finish. In that case the title still says “review incomplete.” Other incomplete reviews stay neutral. A green review check does not mean there are no findings, that deployment is safe, or that Proofline gate allows the merge. Read what Proofline writes on a pull request explains its title, findings and Needs attention block.