The mergesafe-review check

Last updated 2 October 2026.

Can MergeSafe block a merge on GitHub?

Yes: every review sets a mergesafe-review check run on the commit, which fails while any P0 or P1 finding is open, so making it a required status check stops a pull request with blocking findings from merging.

What the check says

• Passed: no P0 or P1 finding is open.
• Issues found: at least one P0 or P1 is open. The check fails.
• Unverified blockers: a P0 or P1 could not be verified. It still fails until it is resolved.
• Coverage incomplete: the review could not cover the whole diff.
• Too large to review: the pull request is over the size limits; the check asks for action.

Its text gives the count of verified findings per severity.

Making it required

1. On GitHub, open the repository’s branch protection or ruleset for the default branch.
2. Require status checks to pass, and add mergesafe-review.
3. Also require an approving review from a person: MergeSafe only comments and never approves on its own.

Both are part of MergeSafe’s Recommendations. To clear a blocking finding, fix it or reply to it; a disputed finding never keeps blocking.

If the GitHub App lacks permission to create checks, the review is still posted without the check.

Next: @mergesafe commands →