actions: restrict concurrency on update-links workflow #441
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
ovflowd
reviewed
May 21, 2025
|
|
||
| concurrency: | ||
| group: update-redirect-links | ||
| cancel-in-progress: false |
Member
There was a problem hiding this comment.
I think it should cancel in progress to start the most recent one, no?
Member
Author
There was a problem hiding this comment.
No, I want whatever runs first to complete, so that you don't end up in a race where one has say created the branch but not the PR, and the second run then collides with the existing branch.
Member
Author
There was a problem hiding this comment.
Suggested change
| cancel-in-progress: false | |
| # Allow existing runs to complete to avoid branch collisions | |
| cancel-in-progress: false |
Worth adding this to clarify?
MattIPv4
changed the title
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.
Should stop the workflow racing itself as seen in #439 + #440