cpo-ship

Ships the queue the owner has approved: merges merge-ready cards to the base branch one at a time, in a safe order, then runs post-merge operations and reports what is left.

When to use it

• one or more cards sit at the merge-ready gate with your approval
• you want to release and close the loop on a batch

What it needs

• a configured repo — branch names and merge target come from config
• cards at the merge-ready state; it merges nothing else. Only the owner sets that state

What you get

• the approved queue merged, one card at a time, with checks between merges
• post-merge operations run, cards moved to done, and a report of what remains on the board

Where it sits

The end of the build lane. It makes no file changes — pages and code are frozen when the branch reaches the merge-ready state. After it runs, cpo-announce and cpo-wiki tell the story of what shipped.

Say this

cpo-ship
merge what I approved
close the loop