docs: gh-merge-green is optional on feat-cmux-next (no bead)
Merged
TE
23d ago+3+3+0123456789-3-3-0123456789
Lawrence and Leo: gh-merge-green is optional on feat-cmux-next, and nothing should tell agents to use it. A plain gh pr merge --squash --match-head-commit <sha> under the branch's rules is fine. The helper's fast gate is in #20566 (main, where the helper lives).
docs/ci/cmux-next-batch.md: by hand, the owner lands a validated PR with a plain merge or the optional helper. Only the queue's own--landuses gh-merge-green.scripts/ci/next_batch.py: the green receipt now says "land it yourself on this receipt (gh pr merge --squash --match-head-commit; gh-merge-green is optional)".
Verification: python3 tests/test_next_batch.py passes (it asserts "land it yourself" in the receipt).
Changelog
none
🤖 Generated with Claude Code
Need help on this PR? Tag @codesmith-bot with what you need.
Summary by cubic
Clarifies that gh-merge-green is optional on feat-cmux-next and that nothing should tell agents to use it. A plain gh pr merge --squash --match-head-commit <sha> is fine under the branch's rules.
- Updates
docs/ci/cmux-next-batch.mdso only the queue's own--landusesgh-merge-green; owners land validated PRs with a plain merge. - Changes the green receipt in
scripts/ci/next_batch.pyto say "land it yourself on this receipt" and note thatgh-merge-greenis optional.