docs(merge-strategy): CodeQL default setup never analyzes fork PRs - #163
Merged
Conversation
Default setup's Analyze contexts, required in classic branch protection, never report on a fork PR head — the PR sits BLOCKED with every visible gate green, and neither the rules endpoint (classic protection is invisible there) nor the rollup (the contexts are absent, not red) names the cause. Documents the GraphQL isRequired diagnosis, the helper-branch workaround that shares the head SHA, and the durable fix of switching to an advanced-setup codeql.yml whose Analyze job matrix reproduces the required context names — including the disable-default-setup-first ordering, without which SARIF uploads are refused. Observed and fixed 2026-08-26 on netresearch/git-workflow-skill (#226, #237, #240). Assisted-by: claude-code:claude-fable-5 Agent-Session: https://claude.ai/code/session_01C7S9rbgu5giqCwnzwafrHA Agent-Host: 0493f0 Signed-off-by: Sebastian Mendel <github@sebastianmendel.de>
Contributor
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
|
CybotTM
marked this pull request as ready for review
August 26, 2026 11:36
Member
Author
|
Self-review: 2715709 The review this pull request demands is unsatisfiable (Copilot quota wall or repeated bot failures on this head). Per the documented fallback, the diff on this head was reviewed by the PR author; this comment is the on-the-record attestation the merge gate reads back. It stops matching on the next push. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.



New troubleshooting section beside the existing default-setup wedge case, from a /retro of today's session: CodeQL default setup does not analyze fork PRs, so where its
Analyzecontexts are required (typically in classic branch protection, invisible to the rules endpoint), every fork PR sits BLOCKED with all visible gates green. Covers the GraphQLisRequireddiagnosis, the helper-branch workaround (identical head SHA in the base repo dispatches the contexts), and the durable fix — an advanced-setupcodeql.ymlwhose Analyze job matrix reproduces the required context names, with the disable-default-setup-first ordering that SARIF uploads demand.Observed and fixed on netresearch/git-workflow-skill today: #226 (the blocked fork PR), #237 (the diagnosis), #240 (the fix).
Assisted by claude-code:claude-fable-5 — Session