2025-02-12 · Noah Fischer
Why we teach merge queues with tabletop stories
Image unavailable
Merge queues feel like plumbing until a single red build freezes a train. We start cohorts with a tabletop: who speaks first, who owns rollback, how we document the decision in the tag notes.
In the second paragraph we walk through a fictional-but-grounded outage where two teams disagree on whether to bypass the queue. The goal is vocabulary, not heroics. Participants leave with a shared script instead of a vague “we should communicate better.”
Finally, we tie the story to artifacts: annotated tags, release notes, and where Git history should carry intent versus where the wiki should. The exercise is short on purpose — it primes the technical modules without drowning newcomers in YAML.