Trunk-Based Development vs. GitHub Flow

“Even after finding that trunk-based development practices contribute to better software delivery performance, some developers who are used to the “GitHub Flow” workflow remain skeptical. This workflow relies heavily on developing with branches and only periodically merging to trunk. We have heard, for example, that branching strategies are effective if development teams don’t maintain branches for too long – and we agree that working on short-lived branches that are merged into trunk at least daily is consistent with commonly accepted continuous integration practices. […] We should note, however, that GitHub Flow is suitable for open source projects whose contributors are not working on a project full time.”

Accelerate by Forsgren, Humble, Kim, et al. 2018

Leave a Reply