Skip to content

fix(ci): stop the CodeQL cron cancelling the main merge scan #7933

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
waleedlatif1 merged 1 commit into from
Sep 17, 2026
Merged

fix(ci): stop the CodeQL cron cancelling the main merge scan #7933

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 9 additions & 1 deletion .github/workflows/codeql.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -62,7 +62,15 @@ on:

concurrency:
group: codeql-${{ github.ref }}
cancel-in-progress: true
# PR runs only. Superseding is what this is for: a PR push makes the previous
# scan of that PR irrelevant, and `refs/pull/N/merge` keeps each PR in its own
# group. The push and schedule triggers both resolve to `refs/heads/main`, so a
# blanket `true` let the daily cron cancel the merge scan of the same commit --
# a 2-minute window that finally landed on 3c8a4c4 (push 08:32:58 killed by the
# 08:34:47 cron), leaving main with a red rollup for a commit that the cron had
# in fact scanned clean. Non-PR events now queue instead: one pending run is
# held per group, so the cron simply waits out the merge scan.
cancel-in-progress: ${{ github.event_name == 'pull_request' }}

permissions:
contents: read
Expand Down
Loading