CI: handle merge_group so enabling a dev merge queue is a safe one-click - #1716
Merged
Conversation
Lands the prerequisite #1715's merge-queue recommendation named: without a merge_group trigger the required 'build' and 'Darling PostgreSQL tests' checks never report inside a queue, and every queued PR stalls - enabling the ruleset before this wiring would brick dev merges. The trigger is inert until the queue ruleset is actually enabled. Queue runs take the same always-restore path as dev/main pushes (a queue run is the last validation before its result lands on dev) and the per-run concurrency group, so they are never cancelled or replaced. Path classification works unchanged: dorny/paths-filter v4.0.1+ resolves merge_group diffs from the payload's base_sha/head_sha whenever the base input is empty, which is exactly what the filter steps pass for non-push events. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
erikdarlingdata
enabled auto-merge
July 26, 2026 21:05
This was referenced Jul 26, 2026
pull Bot
pushed a commit
to ehtick/PerformanceMonitor
that referenced
this pull request
Jul 29, 2026
…lick does not exist on a personal-account repo Merge queues are organization-only (public repos on any plan, private on Enterprise Cloud); creating the recommended ruleset here returns 422 Invalid rule 'merge_queue'. The merge=union .gitattributes alternative is also out - GitHub's server-side PR merging ignores merge attributes (community discussion #9288). The merge_group wiring stays: inert, zero cost, live the day the repo ever moves to an organization. No separate CHANGELOG entry for this PR: it corrects an [Unreleased] entry in place - the change IS the changelog. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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
1 participant
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.
Lands the prerequisite #1715's merge-queue recommendation named: without a merge_group trigger, the required build and Darling PostgreSQL tests checks never report inside a queue, so every queued PR stalls - enabling the ruleset before this wiring would brick dev merges. The trigger is INERT until the queue ruleset is enabled (repo setting; suggested settings in #1715's body).
With this merged, the ruleset click is the ONLY remaining step to kill the CHANGELOG-conflict re-push train.
🤖 Generated with Claude Code