Build: Cancel superseded PR runs in lightweight CI workflows#16771
Open
wombatu-kun wants to merge 2 commits into
Open
Build: Cancel superseded PR runs in lightweight CI workflows#16771wombatu-kun wants to merge 2 commits into
wombatu-kun wants to merge 2 commits into
Conversation
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This was referenced Jun 12, 2026
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.
What
Adds a
concurrency:group with PR-scopedcancel-in-progressto the five lightweight, PR-triggered workflows that did not have one:docs-ci,license-check,zizmor,codeql, andasf-allowlist-check.Why
The ASF GitHub Actions pool is a shared, capacity-limited resource, and infra guidance asks every project to cancel superseded PR runs so stale commits stop holding runner slots. When several commits are pushed to a PR in quick succession, runs triggered by earlier commits keep going even though their results are no longer relevant. The heavy CI workflows (spark, flink, java, hive, kafka-connect, delta-conversion, and others) already cancel superseded PR runs with exactly this pattern; these five lightweight workflows were the remaining gap.
docs-ciis the most valuable to fix because each superseded run holds a scarce macOS runner.Notes
The block is identical to the one already used across the heavy workflows, including the conditional
cancel-in-progress: ${{ github.event_name == 'pull_request' }}so that pushes tomainand scheduled runs (zizmor, codeql, asf-allowlist-check) are never interrupted; only supersededpull_requestruns are cancelled. For the workflows that also run onmainor on a schedule, two overlapping non-PR runs now serialize within the group instead of running in parallel, which is harmless for these short jobs.