Avoid duplicate CI runs on the merge queue - #2921
Merged
Merged
Conversation
Pushing the merge queue branch emits both a `push` and a `merge_group` event, so CI ran twice on the same commit. That caused a failure due to concurrency groups cancelling one of the runs. This replaces the `push` trigger with `pull_request`, so that the event is not fired in the merge queue. This way, CI runs only once.
NSeydoux
enabled auto-merge
September 18, 2026 08:58
emmettownsend
approved these changes
Sep 18, 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
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.
Pushing the merge queue branch emits both a
pushand amerge_groupevent, so CI ran twice on the same commit. That caused a failure due to concurrency groups cancelling one of the runs. This replaces thepushtrigger withpull_request, so that the event is not fired in the merge queue. This way, CI runs only once.