---
title: "Read what Proofline writes on a pull request | Proofline Help"
description: "Proofline reports each review on the pull request in two places: the Proofline check on the reviewed commit, and a thread for each finding it posts on the diff. After a later push, the new review checks earlier findings again and says what it found on their threads."
url: https://proofline.sh/help/pull-request-output/
---

[Help center](/help/)

# Read what Proofline writes on a pull request

Proofline reports each review on the pull request in two places: the **Proofline** check on the reviewed commit, and a thread for each finding it posts on the diff. After a later push, the new review checks earlier findings again and says what it found on their threads.

## Read the Proofline check

Open the pull request's **Checks** tab and select **Proofline**. While the review runs, its title reads **Proofline is reviewing this change**, and the summary says that the result appears there when the review finishes.

When the review ends, the title gives its result:

-   **Proofline review finished: no new findings**, or **Proofline review finished: 2 findings in this run**, when the review checked everything it set out to check.
-   **Proofline review incomplete**, or **Proofline review incomplete: 2 findings in this run**, when part of the review did not finish. The summary then says **Proofline could not finish this review.** The findings it lists are still supported; they cover only the part that finished.
-   **Proofline review skipped**, when Proofline did not review the change, for example because the pull request was not sampled.

The count covers findings from this run only. A finished review with no findings says **No new findings in this review.** That means the review found nothing it could support. It does not mean the change is safe, and findings from earlier runs can still be open. [Configure pull request checks](/help/pull-request-checks/#choose-a-mode) explains when the check turns green.

### Findings

**Findings** lists each finding with its severity, such as **Serious** or **Warning**, its title and the file and line it cites. The title links to the finding's thread on the pull request. When the finding has no thread, the title links to the finding in Proofline, and the check adds **Why it matters** and **Suggested change** beneath it.

A note after a finding says what the pull request already knows about it:

-   **persists from an earlier review**: an earlier review reported the same finding and it is still there. Proofline keeps its existing thread instead of opening another.
-   **reintroduced after being fixed**: the finding was fixed and has come back.
-   **already reported on this pull request**: an earlier review posted it.
-   **dismissed**, **accepted risk** or **ignored on this pull request by command**: someone recorded that decision, and the finding stays visible with it.

When the review has more findings than the check lists, it says **More findings are available in Proofline.**

### Needs attention

**Needs attention** counts what is still open on the pull request, and lists only the counts that are not zero:

-   how many open findings need attention, and how many of them come from this run;
-   how many earlier findings remain open, which the total includes. These are findings an earlier review reported that this run did not report again. Proofline counts them as open, not fixed, and links each one, up to 10, with the rest in Proofline;
-   how many failed CI jobs need attention;
-   how many unresolved Proofline threads there are apart from the findings already counted.

The block can change after the review finishes, as people resolve threads and record decisions on findings, and as CI jobs fail. When the pull request has moved on since the review, it says **This review covers an earlier version of the pull request.** Open the newer commit's check for its result.

**Outside the diff**, when shown, names earlier findings whose cited files the pull request no longer changes. Proofline does not count them as open on this commit and leaves their threads as they were.

### Links

**Change** can carry a line on what the pull request is for, and links its walkthrough, such as **4 steps · Open walkthrough**. The walkthrough can finish after the check; the link appears when it does. **View review details** opens the review in Proofline. See [Read a review](/help/read-review/).

## Read a finding thread

Proofline posts one review comment for each finding it places on the diff. The comment names the severity and title, then explains the defect, what can fail and how to fix it. A finding seen at several places or in several environments is one comment that names them all. **View finding in Proofline** opens the finding.

Reply on the thread to record a decision, such as `fixed` or `dismiss`. See [Use Proofline commands on a pull request](/help/pull-request-commands/#record-a-decision-on-a-finding).

## Read the replies after a later push

When you push again, the new review checks the earlier findings that the push could affect. Proofline reports the result on the finding's newest thread:

-   **Fixed.** Proofline adds a line to the thread's first comment saying **Proofline confirmed this finding was fixed**, with a link to the review, and resolves the thread. It posts no reply. GitHub lets Proofline resolve a thread only when your installation of the Proofline GitHub App has granted **Contents: write**. Without that permission, the line also says that Proofline could not resolve the thread, and the thread stays open for you to resolve. Proofline does not count it as an unresolved thread.
-   **Still present.** Proofline replies **Still present in this version**, and says whether the finding's checks still fail or Proofline found the issue again.
-   **Returned.** When the thread last showed the finding as fixed and the issue is back, the reply reads **Returned in this version** instead.

If someone marked a code finding fixed on the pull request, for example by replying `fixed` on its thread, and a later review finds the issue again, Proofline replies **Still present at** that commit, with where the issue is now if it moved, and reopens the thread if it was resolved.

Proofline posts nothing on a thread when:

-   the new review opened a new thread for the same finding, which states the finding at the new commit;
-   Proofline could not tell whether the fix worked. The finding stays open, and the finding page in Proofline lists the attempt and its reason;
-   the finding cites only files the pull request no longer changes;
-   the finding has no thread on the diff, or GitHub no longer accepts replies on its thread.

## When a review posts only the check

Proofline posts a review comment only when the run has a finding the pull request has not seen yet, or one that came back. A review with nothing new to report, including a review whose findings all persist from earlier runs, posts no comment. Its result is in the **Proofline** check alone, which links the review in Proofline.

Setup work that an administrator can do, such as connecting a source Proofline could not read, appears on the Inbox rather than on the pull request. See [Clear Inbox setup tasks](/help/inbox-setup-tasks/).

## Read the description section

When the repository allows it, a person with write access can ask Proofline to write a review's summary into a marked section of the pull request description. Proofline writes the section only on that request, from the review page; a push or a new review does not update it. See [Write the description section](/help/read-review/#write-the-description-section) for the setting, how to ask and what each outcome means.

## Related guides

-   [Read a review](/help/read-review/)
-   [Use Proofline commands on a pull request](/help/pull-request-commands/)
-   [Configure pull request checks](/help/pull-request-checks/)
-   [Read and act on a finding](/help/findings/)
