forked from molecule-ai/molecule-core
d9f69a8fd5
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> |
||
|---|---|---|
| .. | ||
| auto-promote-staging.yml | ||
| block-internal-paths.yml | ||
| canary-staging.yml | ||
| canary-verify.yml | ||
| ci.yml | ||
| codeql.yml | ||
| e2e-api.yml | ||
| e2e-staging-canvas.yml | ||
| e2e-staging-saas.yml | ||
| e2e-staging-sanity.yml | ||
| promote-latest.yml | ||
| publish-canvas-image.yml | ||
| publish-workspace-server-image.yml | ||
| retarget-main-to-staging.yml | ||