Improve concurrency settings for PR checks - #3405
Merged
mbg merged 6 commits intoJan 21, 2026
Merged
Conversation
Copy link
Copy Markdown
Member
Sorry, something went wrong.
Since `github.workflow` will be the caller's name for `workflow_call` events
Copy link
Copy Markdown
Contributor
There was a problem hiding this comment.
Pull request overview
This PR improves the concurrency settings for PR check workflows by including workflow input parameters in the concurrency group name. This allows workflows with different input combinations to run in parallel while ensuring that workflows with the same inputs and ref are properly grouped for cancellation or queuing.
Changes:
- Modified the Python generator script to append all workflow inputs to the concurrency group name
- Updated the cancel-in-progress expression (added redundant || false clause)
- Regenerated all 61 workflow files with the new concurrency group naming pattern
Reviewed changes
Copilot reviewed 56 out of 56 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
| pr-checks/sync.py | Updated concurrency group generation to include workflow input values; modified cancel-in-progress expression |
| .github/workflows/__*.yml (61 files) | Auto-generated workflow files reflecting the new concurrency group naming pattern with input values |
Sorry, something went wrong.
Comment thread
pr-checks/sync.py
Comment thread
pr-checks/sync.py
Outdated
Comment thread
pr-checks/sync.py
redsun82
previously approved these changes
Jan 21, 2026
redsun82
left a comment
Copy link
Copy Markdown
Contributor
There was a problem hiding this comment.
many thanks for this!
Sorry, something went wrong.
henrymercer
approved these changes
Jan 21, 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
Reviewers
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.
Risk assessment
For internal use only. Please select the risk level of this change:
Which use cases does this change impact?
How did/will you validate this change?
If something goes wrong after this change is released, what are the mitigation and rollback strategies?
How will you know if something goes wrong after this change is released?
Are there any special considerations for merging or releasing this change?
Merge / deployment checklist