ci: add merge_group trigger to block-internal-paths workflow - #1997
Merged
Conversation
Re-do of the fix that was originally bundled into PR #1995 but never landed — the second commit on that branch got rejected by GH006 (branch locked by merge queue) after the first commit was already queued. Only the file-removal commit made it to staging. Without this trigger, adding "Block forbidden paths" to required_status_checks deadlocks the queue: every PR sits in AWAITING_CHECKS forever waiting on a check that can't fire on gh-readonly-queue/* refs. Sequence to land safely: 1. (already done) Removed "Block forbidden paths" from required_status_checks 2. (this PR) Add merge_group trigger 3. (after merge) Re-add "Block forbidden paths" to required_status_checks Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
HongmingWang-Rabbit
enabled auto-merge
April 24, 2026 07:19
![molecule-ai[bot]](https://avatars.githubusercontent.com/u/275794187?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
APPROVE — surgical merge-group trigger fix.
Correctly adds merge_group: types: [checks_requested] to block-internal-paths.yml, which resolves the merge queue AWAITING_CHECKS deadlock that would otherwise block PR #1981 and future queue-backed PRs. The inline comment explaining the why is precise.
CI: all checks green ✅ (CodeQL × 4, Block forbidden paths, Detect changes, all 5 CI skipped jobs).
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.
[Molecule-Platform-Evolvement-Manager]
Re-do of the trigger fix that was bundled into PR #1995 but never landed — the second commit on that branch got rejected by GH006 (branch locked by merge queue) after the first commit was already queued. Only the file-removal commit made it to staging.
Why this matters
Without `merge_group:` trigger, adding `Block forbidden paths` to `required_status_checks` deadlocks the queue: every PR sits in AWAITING_CHECKS forever waiting on a check that can't fire on `gh-readonly-queue/*` refs.
Sequence to land safely
Diff
5 lines added to `.github/workflows/block-internal-paths.yml` — same shape as PR #1982 added to ci.yml + codeql.yml.