---
title: "Find out why a pull request's merge gate is blocked | Proofline Help"
description: "Open the Proofline gate on the pull request's current head. The result distinguishes a blocking finding from an unfinished review or a policy that needs attention."
url: https://proofline.sh/help/diagnose-blocked-merge-gate/
---

[Help center](/help/)

# Find out why a pull request's merge gate is blocked

Open the Proofline gate on the pull request's current head. The result distinguishes a blocking finding from an unfinished review or a policy that needs attention.

## Inspect the decision for the reviewed head

The gate blocks a head when its review is incomplete or an open supported finding meets the chosen severity. When the repository's [agent-authored pull request policy](/help/agent-authored-pull-requests/) is **On**, every open supported finding blocks a pull request it covers. If the review checked an environment, the gate also blocks when that environment's evidence is incomplete or a required deterministic check blocks it. A review that checked no environment is decided on its code findings alone, so an allowed head says nothing about any environment.

Open the pull request's review to inspect the assessments and findings.

Proofline does not review the pull requests it opens, so the gate decides them another way. One it opened under the fix rule is decided by Kian's re-check of the gate's exact commit: the gate allows it only when that re-check found no counterexample to the confirmed problem. That result does not show the fix is safe. The gate blocks it when the re-check found that the problem remains, was incomplete or has not finished, or when Kian has not re-checked that commit. If the re-check had not finished, select **Re-run** on the **Proofline gate** check once the pull request description shows its result. One Proofline opened at a person's request, such as from **Fix all**, **Open a fix pull request** or an `apply fix` reply that opens one, is neither reviewed nor re-checked, so the gate blocks it; a person reviews it.

A head keeps its gate decision. Rerunning the review or resolving a finding on the same head does not change it. Push a commit that addresses the blocking condition, and the new head gets a new review and gate decision.

A gate that blocked before any review started, for example because the author had no seat, can be decided again at the same head. Fix the cause, then select **Re-run** on the **Proofline gate** check in GitHub; you need write access to the repository. Proofline reviews the head, or reuses a review already there, and records a new gate decision with its own check. A review started at that commit another way, such as with the `review` command, replaces the block too. A gate that a review decided keeps its decision.

A pull request whose head adds only an empty commit to a commit already on another protected branch that requires pull requests, such as a promotion between two protected branches, passes the gate without a new review: those commits passed review on that branch. The **Proofline gate** check says so. A merge group of such pull requests passes the same way.

If the review failed, or stopped because Proofline's own run was interrupted, the gate does not decide yet. Proofline reviews the same head once more, and **Proofline gate** stays in progress until that review finishes. If the second review cannot finish either, the gate blocks, and any new commit starts a new review, even one with no changes.

When draft reviews are off, Proofline waits until the pull request is ready before capturing its gate. A head already recorded as **draft not reviewed** by an earlier version needs a new commit, or a **Re-run** of its **Proofline gate** check, after the pull request is marked ready.

## Related guides

-   [Set up a merge gate](/help/merge-gate/)
