---
title: "Trace a shipped pull request that bypassed its merge gate | Proofline Help"
description: "A deployment can carry a pull request that merged while Proofline’s merge gate blocked it. The marker on the deploy records the merge history for that particular pull request."
url: https://proofline.sh/help/deploy-shipped-pr-merge-bypass/
---

[Help center](/help/)

# Trace a shipped pull request that bypassed its merge gate

A deployment can carry a pull request that merged while Proofline’s merge gate blocked it. The marker on the deploy records the merge history for that particular pull request.

## Follow the bypass from the shipped change

Open the deploy and locate the relevant change under **Pull requests**. Look for **Bypassed: the pull request merged while the gate blocked it**. When the marker links to a review, open it to inspect the gate decision for that change.

Read the deployment’s own checks separately. The bypass describes the pull request at merge time. It does not say whether the deployment landed or what happened to the service afterwards.

## Related guides

-   [Check what a repository audit or deployment actually covered](/help/trace-repository-audits-and-delivery/)
-   [Set up a merge gate](/help/merge-gate/)
