Ship-Show-Ask

Ship/Show/Ask is a branching strategy that lets every change carry its own level of review. Ship goes straight to mainline, no PR, no waiting. Show opens a PR but merges without waiting for approval, creates a space for feedback after the fact. Ask opens a PR and waits for input before merging.

Most teams default to Ask for everything, which makes sense when trust is low or the codebase is unfamiliar. But it creates a scaling problem: too many changes waiting on too many reviewers, and the quality of feedback drops as the queue grows. The strategy works because it makes the review decision explicit per change rather than applying the same gate to everything. Slam it shut and move on is the attitude that makes the Ship mode actually work.

Source

Linked from

Last updated August 2021