Repository navigation
/ship asks its go-ahead as a question instead of asking you to type a phrase. Patch: same
delivery plan, same gate, no breaking changes.
Changed
/shipasks "Deliver this plan?" after printing the delivery plan. The options are "Go
ahead" (delivers exactly the printed plan), "Go ahead, and send the chat message" (only when the
plan's chat line is a draft) and "Change something". No option is marked recommended, and any
other answer is a change request, never approval. Runtimes with no question tool still take the
typedgo ahead.ship unreviewedand theyesbefore destructive SQL stay typed. Found in a
teammate run where the person had to typego aheadafter already saying to send.