Add pull_request trigger to linkchecker workflow#248
Conversation
|
Learn Build status updates of commit b5e2fe9: ✅ Validation status: passed
For more details, please refer to the build report. |
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans. ✅ No issues foundMore information about PoliCheckInformation: PoliCheck | Severity Guidance | Term |
The linkchecker workflow was missing a pull_request trigger, so it never ran as a PR check. This adds the trigger so broken links are caught before merging. Also excludes the live branch from push triggers since links are already validated on main. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Dickson-Mwendia
force-pushed
the
link-checker-issue
branch
from
b5e2fe9 to
4404b52
Compare
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans. ✅ No issues foundMore information about PoliCheckInformation: PoliCheck | Severity Guidance | Term |
|
Learn Build status updates of commit 4404b52: ✅ Validation status: passed
For more details, please refer to the build report. |
1 participant
The linkchecker workflow was missing a pull_request trigger, so it never ran as a PR check. This adds the trigger so broken links are caught before merging.