ci: cancel superseded pull request runs - #112
Merged
Merged
Conversation
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.
Summary
New pushes currently leave superseded pull-request runs executing. Cancel older runs of each changed workflow for the same PR so runner time is spent on the latest commit. Other PRs and non-PR runs retain their existing behavior.
.github/workflows/docs.ymlValidation
concurrencychanged.git diff --no-index --checkfound no whitespace errors.actionlint -shellcheck= -pyflakes=passed for every changed workflow.Application suites were not run locally for this workflow-only patch. Keep this PR in draft until applicable CI completes. Live cancellation behavior remains to be checked by pushing again while a PR run is active; a
pull_request_targetworkflow uses the base-branch definition until this change is merged.CI verification snapshot
All reported checks for commit
b51b6f91a424e6d5aa0e8aabdd5a7ee6a651f58chave completed successfully or were intentionally skipped, as of 2026-09-11T16:05:09+00:00. No failing or pending checks were reported.