fix(sdk-python): correct REQUIRED_CONTEXTS context names in merge queue workflow #21
Reference in New Issue
Block a user
Delete Branch "fix/merge-queue-contexts-sdk"
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?
Summary
The
gitea-merge-queue.ymlworkflow setREQUIRED_CONTEXTS=CI / test (pull_request), but Gitea's status API reports contexts asTest / test (3.13) (push)etc. for cron-triggered runs. This mismatch caused the queue script to always see the context as 'missing' and never attempt a merge - blocking all SDK Python PRs.Fix: update
REQUIRED_CONTEXTSto the live API-reported context names (all Python 3.x matrix entries) and restore the SOP checklist gate context which was dropped when the workflow overrode the script defaults.Verification
GET /repos/Molecule-AI/molecule-sdk-python/statuses/mainon live Gitea APITest / test (3.13) (push),Test / test (3.12) (push)Test plan
🤖 Generated with Claude Code
9f6939ea55to8205b511c98205b511c9toa4cf7bc75cSDK-Dev Review ✓
Corrects
REQUIRED_CONTEXTSin the gitea-merge-queue workflow. The SDK Python CI usesTest / test (3.11/3.12/3.13) (pull_request)matrix contexts — the old context names (CI / test) were wrong and would never match.Also correctly copies
gitea-merge-queue.pyinto this repo (same standard script as SDK Python and MCP).Approve.
Pull request closed