---
title: "Find which pull requests shipped in a deployment | Proofline Help"
description: "Open a deployment in the environment’s Deploys list and inspect Pull requests to identify the delivered changes beyond the commit at the head of the release."
url: https://proofline.sh/help/deploy-shipped-pull-requests/
---

[Help center](/help/)

# Find which pull requests shipped in a deployment

Open a deployment in the environment’s Deploys list and inspect Pull requests to identify the delivered changes beyond the commit at the head of the release.

## Follow the shipped changes

**Pull requests** lists what the deploy shipped: the pull request merged as the deployed commit and, for a promotion between two protected branches, each pull request the promotion carried, marked **Promoted**. A deploy of a pull request's head before it merged, such as a staging deploy from its branch, lists that pull request marked **Deployed before merge**, with the review of the deployed commit. Under each one, **Review** links its newest review and names the commit it reviewed. Each finding that review raised follows with its severity and where it stood when the deploy landed: **Open**, **Verified fixed** at the commit where Proofline checked it again and found it gone, **Marked fixed**, **Dismissed** or **Accepted risk**. A fix or decision counts only when Proofline recorded it before the deploy landed. A fix verified on an earlier commit of the pull request counts only when Proofline then reviewed the merged commit too; otherwise it reads **State at landing not established**. A dismissal or accepted risk that had expired by then reads as open. When the state changed after the deploy landed, both appear, such as **Open at landing · Verified fixed** at a commit, followed by when it changed; **Reopened** means the finding is open again. **State at landing not established** means Proofline's records cannot place the change before or after the landing, and the finding never reads as fixed then. When the review also checked another environment, a finding about that environment names it after its title, such as **Staging** on a Production deploy. After them, **Requirement** rows list each confirmed gate requirement the review found a service of this environment violating, and **Finding** rows list the other problems it found in this environment, each with the service it concerns, as the pull request comment listed them. These always read **Open**, since Proofline does not yet record a fix or decision for them. A finding raised on an earlier commit of the pull request and not found again is listed too, so a fix made before merging shows here. When the pull request's review cannot stand for what shipped, the reason appears beside its name: **No review**, **Not reviewed** for a review that never ran (a promotion's own review is excluded), **Review not finished**, **Reviewed an earlier head** when the review did not see the merged commit, or **Environment not checked**. When Proofline recorded why it did not review a pull request, the reason follows, such as a review filter that excludes its branch, author or label, in the words the **Pull requests** list uses. An administrator also sees the repair when a setting causes it, such as **Assign seat** for an author without a seat. A pull request that Proofline opened under the fix rule has no review; it names **Kian re-check** of the merged commit instead, with the conclusion its pull request body gives: no counterexample, the problem remains, incomplete with the reason, or pending while it runs. **Kian re-check** opens the re-check's investigation. When Kian re-checked only an earlier commit, the line says the merged commit has no re-check. A re-check does not check the environment, so the pull request still counts as **No review**. When a pull request merged while its [merge gate](/help/merge-gate/) blocked it, **Merge gate** reads **Bypassed: the pull request merged while the gate blocked it**, as the review's run record does, and links that review. No findings listed does not mean a pull request is safe. When Proofline cannot establish which pull requests a promotion carried, the section says why and lists none of them.

[![Pull requests on a deploy's page. The deployed commit's pull request has a Completed review with two serious findings: The API tasks exceed the database connection limit reads Open, and A failed retry leaves the request lock held reads Verified fixed at landing · Reopened 4 minutes ago. The second pull request reads Promoted, with an Incomplete review.](/help-images/deploy-pull-requests-light.png)](/help-images/deploy-pull-requests-light.png)

The code finding was verified fixed when the deploy landed and is open again. The promoted pull request's review did not finish. Fictional demo workspace.

When the review that covered the deploy belongs to no pull request, a section above **Pull requests** lists it the same way: **Deployment gate** for the review the deploy's deployment gate ran, or **Commit review** for a review of the deployed commit. Its **Review** row names the review's state, such as **Review in progress**, the commit it reviewed and, when the review did not check this environment, **Environment not checked**. Each finding it raised follows with where it stood when the deploy landed.

## Related guides

-   [Read a deploy's verification](/help/read-deploy-verification/)
-   [Turn on the production loop for AWS](/help/aws-production-loop/)
