A flexible, modern approach to the popular git-flow branching model. Download the CLI tool to get started with a better Git workflow: brew install git-flow-next
Worktrees as the default is the change that makes the most sense to me right now. Running a few agents in parallel in one checkout always ends with someone stepping on a half-finished change, so giving each feature its own directory — and cleaning it up on finish — removes a lot of that friction. I'm curious how it handles a worktree when a feature branch already has uncommitted work elsewhere: does it refuse, move it, or leave that decision to the user?
Hey Product Hunt 👋 I'm Bruno from the Tower team, and we also work on git-flow-next.
git-flow-next is the successor to the original git-flow, the branching model that has organized feature, release and hotfix branches for countless teams since 2010. We rebuilt it from scratch in Go, and it's fully compatible with your existing git-flow setups. It's free and open source, and it's endorsed by Vincent Driessen, the creator of git-flow, which means a lot to us.
Version 2.1 adds worktrees, the feature you've asked for most:
Start a feature in its own directory with --worktree, with no more stashing and switching
Jump between worktrees with one command (git flow feature checkout)
Make worktrees the default, so Claude Code, Codex or any other agent that starts a feature gets its own directory, letting them work in parallel without stepping on each other's toes
Finish a feature and its worktree is cleaned up for you
In the AI era, running several agents side by side is quickly becoming the norm, and worktrees are what make that safe.
git-flow-next launched on Product Hunt on October 25th, 2026 and earned 135 upvotes and 3 comments, placing #5 on the daily leaderboard. A flexible, modern approach to the popular git-flow branching model. Download the CLI tool to get started with a better Git workflow: brew install git-flow-next
git-flow-next was featured in Open Source (69k followers), Software Engineering (43.3k followers), Developer Tools (522.7k followers) and GitHub (41.5k followers) on Product Hunt. Together, these topics include over 152.5k products, making this a competitive space to launch in.
Who hunted git-flow-next?
git-flow-next was hunted by fmerian. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how git-flow-next stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
fmerian
Worktrees as the default is the change that makes the most sense to me right now. Running a few agents in parallel in one checkout always ends with someone stepping on a half-finished change, so giving each feature its own directory — and cleaning it up on finish — removes a lot of that friction. I'm curious how it handles a worktree when a feature branch already has uncommitted work elsewhere: does it refuse, move it, or leave that decision to the user?