Trunk-based Development: Ship Every Commit

Learn to ship every commit to production by mastering trunk-based development - no feature branches, no merge conflicts, no drama.


Overview

Ship Every Commit is an intensive, hands-on workshop that transforms how engineering teams deliver software. You’ll learn to abandon feature branches entirely and implement true trunk-based development where every commit goes directly to main and deploys to production multiple times per hour. This workshop covers the technical practices, team disciplines, and cultural shifts required to achieve continuous delivery at the commit level.

Through practical exercises and real-world scenarios, you’ll master feature flags, automated testing strategies, rollback mechanisms, and the mindset changes needed to ship confidently without branches. You’ll discover how companies like air up achieved 8,000 deployments in 6 months and why zero-branch development is the foundation of high-performing engineering teams.

This workshop draws from proven case studies and battle-tested techniques used by world-class consultants. Whether your team is stuck in Git Flow hell or looking to accelerate delivery, this workshop provides the concrete steps to eliminate merge conflicts, reduce cycle time, and ship value continuously.

Workshop Overview:

Foundation & Mindset

  • Why branches slow you down: the hidden costs of feature branches
  • The psychology of shipping: building confidence to deploy every commit
  • Continuous integration vs. continuous delivery vs. continuous deployment

Technical Practices

  • Trunk-only Git workflows: committing directly to main
  • Feature flags and progressive rollouts
  • Automated testing strategies that enable safe commits
  • Rollback and rollforward mechanisms
  • Database migrations in a continuous delivery world

Team Practices

  • Pair programming and ensemble programming for quality
  • Small commits and atomic changes
  • Code review alternatives that don’t block flow
  • Monitoring and observability for rapid feedback

Organizational Change

  • Breaking down silos between dev, ops, and business
  • Building psychological safety for frequent releases
  • Metrics that matter: lead time, deploy frequency, MTTR
  • Case studies: air up, Springer Nature, and other success stories

Target Audience

Engineering teams, tech leads, and CTOs who want to eliminate deployment friction and achieve true continuous delivery. Suitable for teams currently using Git Flow, GitHub Flow, or any branching strategy.

Prerequisites

Basic Git knowledge and experience with CI/CD pipelines. Participants should bring laptops with development environments configured.

Learning Outcomes

  • Implement zero-branch Git workflows safely
  • Design feature flag strategies for gradual rollouts
  • Build automated testing that enables confident commits
  • Establish team practices that support continuous shipping
  • Transform organizational culture to embrace frequent releases