Repository navigation
ci: run on merge_group and keep publishing off the queue ref - #3
Merged
Merged
Conversation
Enables a GitHub merge queue without changing release behaviour: CI runs for merge_group so queued merges can satisfy required checks, while the publish job only runs for push and workflow_dispatch. A merge-group run must never publish.
|
Beta prerelease published: |
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.
Change
Enables a GitHub merge queue for
mainwithout touching release behaviour:merge_grouptrigger, so queued merges get a CI run that can satisfy the required checks;publishtopushandworkflow_dispatch. Amerge_grouprun executes on a syntheticgh-readonly-queue/...ref, and the oldevent_name != 'pull_request'guard would have treated that as a releasable push.PR pre-release jobs are unaffected (they already require
pull_request).Why
Branch protection is strict (branch must be up to date), so landing several PRs means update-branch + a full CI cycle for each one, serially. The merge queue does that automatically.
Validation
YAML parses and
on:lists all four events. CI on this PR is the real check; after merge the first queued PR exercisesmerge_group.