Repository navigation
Conversation
CodeQL SAST keyed its concurrency group by commit SHA on push events, so every merge to main got its own group and nothing was ever cancelled; OpenSSF Scorecard had no group at all. On 2026-10-04 a day of 36 merges queued one CodeQL analysis (40-100 minutes each) and one Scorecard run per merge, ahead of every pull request run: pull request CI waited hours for a runner, and a main analysis waited 4 hours. CodeQL now groups by event and by pull request number or ref, so pull requests keep one analysis each as before, and a newer push to main cancels the analysis of an older main commit. Scorecard groups by ref with the same cancellation. Only the newest main commit matters for both: code scanning tracks the default branch's latest analysis. DCO keeps its per-commit group on purpose: its push run on main is the check that catches a merge rewriting sign-offs, so a superseded push must still be checked, and a DCO job takes seconds. Signed-off-by: Martin Vogel <martin.vogel.tech@gmail.com>
This branch has not been deployed
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
1 participant
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.
What
CodeQL SAST and OpenSSF Scorecard analyse only the newest main commit. A newer push to main cancels the run of an older one.
Why
CodeQL SAST keyed its concurrency group by commit SHA on push events, so each merge to main got its own group and nothing was ever cancelled. Scorecard had no group. On 2026-10-04, a day of 36 merges queued one CodeQL analysis (40-100 minutes each) and one Scorecard run per merge, ahead of every pull request run:
Changes
.github/workflows/codeql.yml: the group is nowcodeql-<event>-<PR number or ref>.codeql-gateis unaffected..github/workflows/scorecard.yml: new groupscorecard-<ref>withcancel-in-progress.Code scanning tracks the default branch's latest analysis, so skipping intermediate main commits loses no alert.
Verification
Both files parse (Ruby YAML) and contain only ASCII. Each concurrency block is 2 keys.