From the course: Git for Teams

Unlock the full course today

Join today to access over 22,600 courses taught by industry experts or purchase this course individually.

Trunk-based development

Trunk-based development - Git Tutorial

From the course: Git for Teams

Start my 1-month free trial

Trunk-based development

“

- [Instructor] In this lesson, we'll discuss the trunk-based development workflow. Trunk-based development is a rather new workflow. Teams practicing trunk-based development only collaborate on a single branch named trunk. Under this strategy, trunk is the only long-lived branch used by the team for pulling, syncing, or merging. Some teams practicing trunk-based development will allow branching from trunk for release branches or other short-lived branches used for code reviews. In general, branching from trunk, such as when using a feature branch, is not acceptable. With few exceptions, developers commit directly to trunk. You might wonder why a team would give up the flexibility of working in multiple branches. The selling point behind Trunk-Based Development or TBD is that it reduces the problems that frequently occur when merging long-lived branches such as breaking the build, duplicate work, and incompatible changes. By focusing all development work on the lone trunk branch, the…

Contents