Repository navigation
ci: run the checks for merge queue groups - #176
Merged
Merged
Conversation
The merge queue tests each pull request on top of the latest main before it lands. Verify is the required check, so CI must also run on merge_group events, or a queued pull request would wait forever. A merge group is scoped like a pull request, against the group's base commit, and like a pull request it only reads the caches and skips the nightly-only DuckShop and fuzz jobs.
kvlonge
force-pushed
the
ci/merge-queue
branch
from
November 11, 2026 09:58
99e8156 to
ae47221
Compare
kvlonge
enabled auto-merge (squash)
November 11, 2026 09:58
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
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.
Why
SQLQuack's main requires branches to be up to date before merging. Each merge forces every other open pull request to update and rerun its ~30-minute CI. A merge queue tests each pull request on top of the latest main and merges it, with no manual updates. The queue needs the required
Verifycheck to run onmerge_groupevents; today CI runs only onpull_request, schedule and dispatch, so a queued pull request would wait forever. Pull Request Metadata and the version guard already handlemerge_group.Changes
ci.ymlalso runs onmerge_group.select_replay scopeandEVIDENCE_BASEuse the group'sbase_sha.The ruleset switch from "require up to date" to the merge queue is a separate repository setting, applied after this merges.
Verification
actionlint1.7.7 passes on the changed workflow (and on main's).ci.ymlis a full-replay path, so this pull request's own run replays every case.