---
title: "Read a review | Proofline Help"
description: "Read Proofline’s review of your code changes and, when the review carries one, its assessment for each environment."
url: https://proofline.sh/help/read-review/
---

[Help center](/help/)

# Read a review

Read Proofline’s review of your code changes and, when the review carries one, its assessment for each environment. Assess the evidence before deciding whether to change the code.

To investigate a specific check, charge or follow-up, [triage the pull request’s review](/help/triage-a-pull-request-review/).

[![A completed pull request review's Overview tab lists two serious findings, each with its cited lines, Impact, Recommended action and the Confirm, Dismiss, Mark fixed and Accept risk buttons, beside Rerun review and the run's status, in the fictional Northstar Demo workspace.](/help-images/review-light.png)](/help-images/review-light.png)

The Overview leads with the findings to address; the side column holds the run's actions and status. Fictional demo workspace.

## Check the change

Open the review from **Reviews** or its pull request. Confirm the repository, commit, and environment match the change you are investigating.

If the review is queued or still running, wait for it to finish before reading the results. While it waits, the review says what for: a free worker and since when, or a scheduled check or GitHub's rate limit and when it continues. If an attempt did not finish, it says when Proofline tries again and gives a support reference. If someone stopped the review, a **Stopped** notice names the person and says whether they stopped it with a comment on the pull request or from Proofline.

Open the review's **Details** tab for the run's record. **Reviewed** shows the base and head commits the review read, with line counts when recorded; select the commit range, such as `1a2b3c4d5e..6f7a8b9c0d`, to open that exact comparison on GitHub. It also says when the pull request has new commits since the run. **Started**, **Took** and **Scope** say what started the run, how long it took and how much of the change it covered. **Cost** shows the credits the run was charged, or has used so far while it runs. **On GitHub** links Proofline's review comment and check, or says why the review was not posted. It also counts the Proofline threads still unresolved on the pull request and links them. **Merge gate** shows the gate decision recorded for this run: **Waiting for this review**, **Deciding**, **Allowed**, **Blocked** with the number of open findings at the gate's severity, **Blocked when the pull request merged**, or **Replaced by the gate on a newer commit**. Whether GitHub requires the check, and so whether the decision stops a merge, depends on the repository's branch rules. **Deep Review**, when shown, says that this run is a [Deep Review](/help/deep-review/), or whether one started automatically, was not needed, could not start or was not evaluated, with the reason. **Review policy**, when shown, carries the sentence about authorship from the [policy for agent-authored pull requests](/help/agent-authored-pull-requests/) when that policy was not applied to the run.

**Checks** lists the GitHub checks on the reviewed commit, as the pull request shows them. Under a failing check, Proofline adds what it found in the job's log: whether the failure looks caused by this change, also fails on the base branch, or looks flaky, with the failed step and the end of the log. **Not reviewed** lists changed files the review skipped, such as generated files, and why.

For a pull request, the **Changes** tab opens files and findings together in Proofline. See [Inspect reviewed changes](/help/review-changes/).

## Read the walkthrough

The walkthrough links each step to the lines it read at the reviewed commit. [Trace a pull request walkthrough to its code](/help/trace-review-walkthrough/).

## Read the findings

The review page starts with what is left to address, such as **1 warning to address**, and lists the findings with the most severe first. Each finding shows the cited file and line and what can fail; open **Impact** or **Recommended action** to read them. A finding that someone has dismissed, marked fixed or accepted no longer counts toward the headline. When every finding has a decision, the headline reads **Every finding has a decision**. After the pull request merges or closes, the headline names that state, such as **Merged with 1 warning open**. A review that is not a pull request run reads **Findings unavailable** when Proofline could not read its current findings; that is not a result of no findings. A **Not published** notice under the environments means the result is not on the pull request; see [Rerun a review](/help/rerun-review/) to publish it.

Under the headline, a pull request review lists each environment linked to its repository and whether this review checked it: **Checked**, **Checking**, **Not checked** or **Not applicable**. Not checked and Not applicable usually give the reason, such as that Proofline does not check this environment for pull requests, or that pull request reviews are turned off for it. When no cloud account is connected to the environment, or its cloud role refused the reads the check needs, an administrator also reads that cause with the step that repairs it: Connect an **AWS account**, **Google Cloud project** or **Azure subscription**, or **Grant the reads**. A member reads **Not checked** alone for those two causes. A pull request from a fork is not checked against an environment. The findings say nothing about an environment the review did not check.

Each finding shows the cited lines from the change above its explanation. Below it, record your assessment with **Confirm**, **Dismiss**, **Mark fixed** or **Accept risk**. When available, **Copy fix prompt** copies a prompt for a coding agent, **Generate a fix** asks Proofline for a fix, and **Post to pull request** posts a finding Proofline did not comment on. **GitHub comment**, beside the finding's severity, opens its inline comment on the pull request. The copy icon at the right of the finding's header copies a link to that finding on this run; the link opens the review with the finding in view and its **Impact** and **Recommended action** open. **Runs** in the side column lists the latest runs of the pull request; when the pull request has more runs than it lists, a link such as **All 8 runs** opens the full history.

## Respond to a finding

Your decision affects how later runs treat the finding. It leaves the existing GitHub thread and earlier gate decisions in place. [Decide whether to confirm, dismiss or accept a finding](/help/decide-review-finding/).

## Read what the review cannot vouch for

An incomplete run can have findings and still leave parts of the change unchecked. The notice on the review names what stopped. [Recover from an incomplete code or environment review](/help/recover-incomplete-review/).

## Share a review of a public repository

Readers of a public pull request can open its published review without signing in. Private evidence and conversations stay inside the organization. [Share a public pull request review](/help/share-public-review/).

## Read test coverage

Compare **Tested commit** with **Reviewed head**, especially when the report came from a merge commit. [Inspect the changed lines a coverage check missed](/help/inspect-reviewed-line-coverage/).

## Follow a finding

Open a finding to read what can fail, why the change causes it, and which evidence supports the explanation. Compare the suggested correction with your intended behavior.

An earlier finding can remain open when this run has no new findings. The headline counts it. Select its **still open** link on the review to read the original finding. The link identifies the earlier run; it does not verify a fix. On the pull request, Proofline replies on the finding's thread after a later push; see [Read what Proofline writes on a pull request](/help/pull-request-output/).

Use [Read and act on a finding](/help/findings/) for the next steps. If the code or environment changes, run a new review rather than treating the old result as current.

## Read research and publish a candidate

A research candidate stays in the console until someone with current repository write access requests publication. [Research a pull request and publish a candidate finding](/help/publish-research-candidate/).

## Write the description section

The repository must allow requests and the GitHub description must contain a marker for the section Proofline can update. [Add a reviewed summary to a pull request description](/help/update-pr-description/).

## Check whether the pull request merges

The pull request's runs page shows what GitHub recorded about its base branch and mergeability. [Check a pull request against its current base branch](/help/inspect-pr-base-branch/).

## Follow the pull request to its deploys

Once a deploy ships the pull request, **Deploys** in the side column of its review and runs pages names each environment it went to that you can see. It leaves out removed environments, and it stays hidden when your access is limited to some repositories, so a missing section does not establish that the pull request never deployed. Each entry shows where that deploy's verification stands and when it landed; select it to open the deploy's page. When one environment holds several deploys that shipped the pull request, such as two programs of one release, the section names the environment once and lists its deploys beneath it. Each is named by its deployment task, with its GitHub Environment when two share a task and its attempt when a landed job re-ran. A deploy ships the pull request when GitHub merged it as the deployed commit, when it was merged since the previous deploy of the same environment and task, when a promotion carried it, or when the deploy ran the pull request's head before the merge and its checks used that head's review.

A deploy that took the pull request back out reads **Removed**. It is a rollback: a later deploy to the same environment, by the same deployment task or the same AWS pipeline or app, of a commit that merged before the pull request, such as a re-run of an earlier workflow run. A pull request that a promotion carried is removed with that promotion. Each environment lists its deploys earliest first, so its last entry is the newest deploy that shipped or removed the pull request. A later deploy that did neither is not listed, so the section does not establish what the environment serves now.

## Request a person or team

Choose a person or team under **Reviewers** on the pull request or review page. [Request or remove a GitHub reviewer from Proofline](/help/request-github-reviewer/).

## More tasks

-   [Inspect a failed CI job from a review](/help/inspect-failed-ci-job/)

[Inspect the inputs behind an environment assessment](/help/inspect-an-environment-assessments-recorded-inputs/).

## Related guides

-   [Read and act on a finding](/help/findings/)
-   [Rerun, stop, or publish a review](/help/rerun-review/)
-   [Review a pull request in depth](/help/deep-review/)
-   [Inspect reviewed changes](/help/review-changes/)
-   [Ask questions about a review](/help/review-questions/)
