Pull request scans
Pull requests with merge conflicts
Why Lighthouse holds scans on conflicted pull requests, and how to scan one anyway.
When a pull request has merge conflicts, the merged code isn't known yet, and the pull request will change once the conflicts are resolved. By default, Lighthouse holds the scan instead of spending credits on a result that will soon be out of date.
What you'll see
On GitHub, the check shows Action required with this message:
This pull request has merge conflicts. Lighthouse did not auto-scan. Resolve the conflicts to scan automatically, or scan anyway.
In Lighthouse, the scan is listed as Skipped: merge conflicts.
What to do
| Option | How |
|---|---|
| Resolve the conflicts | Push the resolved branch. Lighthouse scans it automatically. |
| Scan now | Press Scan anyway on the check in GitHub, or on the scan in Lighthouse. |
Always scan conflicted pull requests
Open the repository's Settings › Scan policy and set Pull requests with merge conflicts to Scan.
Still stuck after reading this page?