The check and the comment
Read the Lighthouse result on a GitHub pull request.
Lighthouse reports a pull request scan in three places on GitHub, and in full in the dashboard.
The check
| Result | Meaning |
|---|---|
| In progress | Lighthouse is scanning the changes. |
| Passed | The scan finished, and nothing reached the blocking policy. Lower-severity findings may still be listed. |
| Failed | The scan found something at or above the blocking policy: This check failed because the repository blocking policy was reached. |
| Neutral | Lighthouse couldn't scan. It failed, was cancelled, or your team is out of credits. The check doesn't block the merge. |
| Action required | The pull request has merge conflicts, and the scan is on hold. See Merge conflicts. |
Open the check's details for the summary and a link to the scan in Lighthouse.
Annotations
Each finding is pinned to its line in Files changed, titled with its severity, such as HIGH: Invoice export skips the owner check.
The comment
With Comment with findings on, Lighthouse posts one comment that lists the findings and links to each location. Later pushes update the same comment.
In Lighthouse
Every pull request scan is listed under Scans (filter: Pull requests) and on the repository's Scans tab. The scan page links to the pull request and shows each finding in full. From there, admins and maintainers can mark false positives, and the check on GitHub updates to match.