Repository navigation
fix: succeed on merge queue groups instead of skipping - #5
Merged
Merged
Conversation
A run whose only job is skipped concludes as skipped, which the organization ruleset may not accept for a required workflow. A no-op job on merge_group makes the run conclude as a success.
chio-labs-delivery
Bot
deleted the
fix/auto-merge-merge-group-success
branch
November 11, 2026 22:04
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.
Follow-up to #4. On merge groups the run now concluded as skipped (its only job is skipped), and the organization ruleset's required-workflow rule may only accept a successful run. A no-op merge-group job makes the run conclude as a success; pull request behaviour is unchanged. Checked with actionlint; the live test is the next sqlbuild merge group.