ci: cancel stale Go Tests runs on force-push#5738
Merged
eriknordmark merged 1 commit intolf-edge:masterfrom Apr 3, 2026
Merged
ci: cancel stale Go Tests runs on force-push#5738eriknordmark merged 1 commit intolf-edge:masterfrom
eriknordmark merged 1 commit intolf-edge:masterfrom
Conversation
Contributor
|
@rucoder can you rebase on master so we can get the yetus to run. |
Add concurrency group to the Go Tests workflow so that a new push to the same branch (or PR update) automatically cancels any in-progress run for the previous commit. Without this, force-pushing a PR branch accumulates multiple parallel Go Tests runs that hold runners and produce stale results. Signed-off-by: Mikhail Malyshev <mike.malyshev@gmail.com>
cc8843e to
f1398ba
Compare
Contributor
Author
|
@eriknordmark rebased |
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.
Description
Add
concurrencygroup to the Go Tests workflow so that a new push to the same branch (or PR update) automatically cancels any in-progress run for the previous commit. Without this, force-pushing a PR branchaccumulates multiple parallel Go Tests runs that hold runners and produce stale results.
How to test and validate this PR
Changelog notes
No user-facing changes.
PR Backports
Checklist
I've provided a proper description
I've written the test verification instructions
I've set the proper labels to this PR
I've checked the boxes above, or I've provided a good reason why I didn't
check them.