The Ultimate Git Flow: Trunk-Based Development and Stacked PRs for the Win
Hmm, the title sounds a bit clickbaity, doesn't it? However, I would like to take the time to discuss the git flow I'm using, what it entails, and why I believe it is essential for high-performing teams in this article. As always, I write this articl...
Responses
Markdown supported · ⌘↵ to post
Ezequiel Leonardo Castaño
I believe the definition of trunk-based development presented is not aligned with the widespread one. Trunk-based development is a methodology where "everyone works in the main branch" and, if there are other branches, they are short-lived, i.e. less than a day.
That would render Stacked PRs as basically the opposite of trunk-based development, since to stack PRs, one assumes a single PR (and thus a branch), will live for several days because otherwise it would not be worth the overhead.
Have a look a this talk from MSFT: Git patterns and anti-patterns for successful developers : Build 2018