Skip to content

fix(ci): never cancel a pull request's Queue check #539

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
kixelated merged 1 commit into from
Nov 3, 2026
Merged

fix(ci): never cancel a pull request's Queue check #539

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
12 changes: 6 additions & 6 deletions .github/workflows/queue.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,12 +31,12 @@ on:
permissions:
contents: read

# Each group has its own ref, so a group never cancels another; a pull request's
# skipped runs replace their own. Dispatches all run on main, so each PR head's
# report has its own group too.
concurrency:
group: queue-${{ github.ref }}-${{ inputs.sha }}
cancel-in-progress: true
# No concurrency group. A pull request's `Queue` job waits on `build` before it
# skips, so cancelling the run then, as a second event for the PR would,
# reports `Queue` cancelled and fails the requirement; even a group without
# cancel-in-progress cancels a pending run. Each merge group has its own ref, so
# its run never had another to replace, and a repeated dispatch only reports the
# same skipped context twice.

jobs:
# The build runs in queue-build.yml so its runner group can admit that
Expand Down