---
title: "Discussion on \"The Ultimate Git Flow: Trunk-Based Development and Stacked PRs for the Win\" | Hashnode"
description: "Discussion on \"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.\nAs always, I write this articl..."
url: "https://hashnode.com/posts/the-ultimate-git-flow-trunk-based-development-and-stacked-prs-for-the-win/63d98f629ea6f9bb612b591b"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [The Ultimate Git Flow: Trunk-Based Development and Stacked PRs for the Win](https://jukben.codes/the-ultimate-git-flow-trunk-based-development-and-stacked-prs-for-the-win?utm_source=hashnode&utm_medium=feed)

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...

Jan 31, 2023 · 10 min read · jukben.codes  
Updated Feb 2, 2023  
Read the article

-   [#github](https://hashnode.com/tag/github)
-   [#pull-requests](https://hashnode.com/tag/pull-requests)

## Written by

[Jakub Beneš](https://hashnode.com/@jukben)

@jukben · Prague, CZ

  
[View profile](https://hashnode.com/@jukben)

I went full circle – from IC to EM, and now I'm back. I focus on technical leadership and internal platforms.

👋 Hey! I'm Jakub Beneš, a Software Engineer based in Prague. I'm passionate about scaling engineering, organizational design, and leadership. I'm a huge fan of web technologies and modern approaches within this field. While I'm a strong contributor on the frontend side, lately, I've been focusing more on the entire stack and infrastructure because there's often low-hanging fruit that can deliver a massive impact – and I enjoy seizing such opportunities. I'm not sure if I'll ever start liking YAML, though. 🤓

## Responses 1

Markdown supported · ⌘↵ to post

[Ezequiel Leonardo Castaño](https://hashnode.com/@ELC)

[Nov 22, 2023](https://hashnode.com/posts/the-ultimate-git-flow-trunk-based-development-and-stacked-prs-for-the-win/63d98f629ea6f9bb612b591b/comment/655e909e84fcf8866e4b956b)

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

[Jakub Beneš](https://hashnode.com/@jukben)

[Nov 24, 2023](https://hashnode.com/posts/the-ultimate-git-flow-trunk-based-development-and-stacked-prs-for-the-win/63d98f629ea6f9bb612b591b/comment/655e909e84fcf8866e4b956b#reply-656123ce29658b9b067c0ce2)

Thanks for the feedback, that’s interesting perspective, never thought about it in this way - actually, I agree with the definition of trunk-based flow as you described it. However, I don’t feel stacked PRs are strictly against it - I think it’s rather complementary to the methodology.

The whole point I wanted to make is how to stay productive if one has bigger changes in mind - definitely not something what’s happening to me often. But it’s super helpful to have easy way how to split a big PR into smaller ones without Git gymnastics and with auto tracking of its parent.