Follow an automatic fix from confirmation to merge

Open the confirmed problem in the environment's Latent risks page and find its Automatic fix line. From there you can follow validation, the GitHub draft and later scans of the same resource.

Read the fix status#

On Latent risks, a line that starts with Automatic fix under each confirmation shows what its fix did:

  • Proofline is writing a fix: the fix is in progress. This can take several minutes.
  • opening a draft pull request: the fix passed validation, and Proofline is opening the pull request.
  • draft pull request means GitHub last reported the pull request as a draft. Select the link to open it on GitHub.
  • pull request appears when GitHub reports the pull request ready for review, or while Proofline waits for its first status from GitHub. If someone converts it back to a draft, the label changes again. The line also shows when Proofline marked it ready after a re-check found No counterexample.
  • Kian re-check of the fix commit follows the number of an open pull request, with the re-check result: pending, No counterexample, Counterexample, or Incomplete with the reason. The fix commit is the newest commit Proofline recorded for the pull request. Select fix commit to open that commit in the pull request on GitHub, where you can compare it with the pull request's latest commit. Select Kian re-check to open that re-check among the environment's investigations. Read a fix pull request's re-check explains each result.
  • Proofline could not post this result to the pull request.: Proofline could not write the result to GitHub, so the pull request body has no Kian re-check section for it. The sentence reads Proofline could not post this result to the pull request or mark it ready. only after No counterexample on a draft that the live rule opened, because posting that result is what would have marked the draft ready. A pull request already ready for review needs no marking. A draft whose rule was changed or turned off gets one readiness statement instead, Proofline will not mark it ready for review, described below. After a failure, Proofline tries once more 15 minutes later, and the sentence disappears when that succeeds. If the sentence remains, Proofline does not try again. Read the result on this line and in the investigation. If it is No counterexample, review the draft and mark it ready on GitHub yourself. Otherwise, or to have Proofline check again, push a commit to the pull request, which starts a new re-check.
  • Proofline will not mark it ready for review: the rule that opened the draft was changed or turned off, and a pending re-check is not shown. Turning the rule on again does not change that, because a new rule does not take over an earlier rule's drafts. Review the draft yourself and mark it ready on GitHub when it is.
  • closed without a merge: someone closed the pull request on GitHub without merging it.
  • merged: someone merged the pull request on GitHub. The line then names what the newest scan since the merge recorded. A merge does not apply the change to the environment, and one scan that no longer reports the problem does not mean it is fixed.
    • no longer reports the problem or still reports it: select The scan of to find that scan under Recent scans.
    • No scan since the merge has recorded the problem or its absence: this can appear even when Recent scans lists a later scan, because a scan with an evidence gap records neither a sighting nor an absence.
    • no longer reported the problem before the merge: scans had already stopped reporting the problem before the pull request merged. The line names the last scan before the merge, so the merge does not count as fixing it.

Search help

Tab to a result. Enter to open. Escape to close.