Intermediate

Branching Models That Survive Code Review

Translate branching policy into daily moves. Compare GitFlow slimmed for SaaS, release trains, and feature flags. You will practice opening pull requests with risk callouts, screenshots for UI, and rollback notes suited to regulated teams.

What arrives in your repo

  • Branch naming workshop with real examples
  • PR description rubric used by mentors
  • Simulation of hotfix while main is frozen
  • Metrics on lead time for changes (interpretation only)
  • Role-play review comments in English and JP notes
  • Checklist for tagging reviewers across time zones
  • Lightweight diagramming for branch graphs

Outcomes we ask you to evidence

  1. Pick a branching approach for a two-team product
  2. Author PRs reviewers can approve without ping-pong
  3. Document rollback expectations per change type

Participant questions

We compare it honestly; most teams adopt a slimmer variant — you will see why.

Experience notes

“Branching Models course forced us to retire mystery long-lived branches — naming section alone saved hours.”

— Mika · Logistics SaaS · 4/5 · Google

“Hotfix drill felt theatrical until we realized our on-call doc was missing rollback owners.”

— Ravi · Tech lead