-
Notifications
You must be signed in to change notification settings - Fork 719
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix merge group cancelling issue #4957
Conversation
ba236aa
to
11040ff
Compare
@newhoggy please make sure to keep notes about this in the knowledge base doc on merge queues. Under "common complications" with an analysis and solution. This won't be the last time we encounter this 😅 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please add comments to the changes otherwise it's difficult to discern why we have named the concurrency groups this way. The link to the github comment would also be useful in the comments.
The fact that we have to replicate this over so many files is a bit ... dissatisfying, it feels like this is going to easily lead to divergence? Do we need a GHA linter? |
11040ff
to
96c11be
Compare
🙈 the replication everywhere. But let's fix that in a different Pr and get this merged to prevent unnecessary merge queue cancellations. |
When more than one PR gets added the the merge queue, the earlier ones might cancel due to our concurrency policy. This is to prevent that.
See https://github.com/orgs/community/discussions/46757?sort=top#discussioncomment-4980818