fix(ci): correct merge-queue context + delete obsolete auto-promote (mcp-server) #46
Reference in New Issue
Block a user
Delete Branch "fix/mcp-server-merge-queue-plus-cleanup"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Two fixes:
gitea-merge-queue.yml:
PUSH_REQUIRED_CONTEXTSwas copy-pasted from molecule-core asCI / all-required (push), but mcp-server's CI job istest. The queue would pause forever waiting for a non-existent context. Corrected toCI / test (push).Delete auto-promote-staging.yml: Trunk-based migration complete — no staging branch exists. The workflow is obsolete and uses GitHub CLI (
gh api) which returns HTTP 405 on Gitea 1.22.6.Refs: #2355, molecule-core 08e8d325.
5-axis review on current head
30051570bb.Correctness: deletes the obsolete staging auto-promote workflow and preserves the mcp-server merge-queue workflow, updating only PUSH_REQUIRED_CONTEXTS from CI / all-required (push) to this repo's actual CI / test (push) context.
Robustness: removes the dead GitHub-era staging promotion path; merge queue remains present and avoids the prior over-delete.
Security: removes the gh/GITHUB_TOKEN gate-read fail-open path; no new credential or auth surface.
Performance: no runtime impact.
Readability: narrow workflow cleanup with explanatory comments.
CI combined status is success and PR is mergeable=true.
Approved. Verified live head
30051570bb: diff is limited to deleting obsolete auto-promote-staging.yml and correcting gitea-merge-queue PUSH_REQUIRED_CONTEXTS to CI / test (push), matching ci.yml job test. CI is green and mergeable=true; #2355 merge-queue capability otherwise preserved.