This page is part of my personal knowledge database, that helps me to store and navigate my learnings.
Read on here for details

Trunk Based Development

ยท 2 minute read

Trunk Based Development is the practice of small, often merges / commits into mainline in a Version Control System, with Trunk being the mainline branch (main, master, production, …)

This workflow is a counter-proposal to branch-focused workflows, like Gitflow, that allow multiple developers to work in parallel in their dedicated “feature branches” for long(er) time.

The assumption is that complexity in merge (the various dev branches) is a function of time and (branch) amount. This complexity will cause pain. Hence the goal of Trunk Based Development is to minimize time spend in merging / synchronization efforts.

The Trunk Based Development workflow supports Single Piece Flow and supplements processes that are tested and released automatically, which is striven for in DevOps. In short: It makes Continuous Integration possible.


Reinforcing Feedback Loops