fix(checks): Add event action to concurrency group name#196
Merged
chris3ware merged 1 commit intomainfrom Apr 11, 2025
Merged
Conversation
Contributor
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
chazypro
approved these changes
Apr 11, 2025
3ware-release Bot
pushed a commit
that referenced
this pull request
Apr 11, 2025
## [4.20.1](v4.20.0...v4.20.1) (2025-04-11) ### Bug Fixes * **checks:** Add event action to concurrency group name ([#196](#196)) ([372f02c](372f02c))
Contributor
|
This PR is included in version 4.20.1 |
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
2 participants
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.
Downstream workflows are being cancelled when renovate rebases as PR. This occurs because renovate will often update the title (edited event) and then force push any changes (synchronize event). Workflows triggered by edited events are being cancelled by workflows triggered by synchronize events because the concurrency group names are the same. Adding
github.event.actionto the concurrency group name should ensure they are unique for different events.