git-flow-next 1.0 is here! #64
alexrinass
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
We're excited to announce the official 1.0 release of git-flow-next — a modern, production-ready reimplementation of the git-flow branching model, written in Go.
What is git-flow-next?
git-flow-next is a ground-up reimplementation that maintains full compatibility with both the original git-flow and git-flow-avh, while bringing modern features and flexibility to your Git workflow.
Key Features
Full git-flow & git-flow-avh Compatibility
Switch to git-flow-next without disrupting your existing workflow. Your current configuration is automatically detected and translated at runtime — no migration steps required. When you're ready for the new features, just run
git flow initor usegit flow config.Fully Customizable Branch Configuration
You're not locked into the traditional git-flow structure. Configure any branch hierarchy that suits your team — from simple GitHub Flow (
main+ feature branches) to complex multi-environment GitLab Flow setups, or something entirely custom with your own branch types.Three Built-in Workflow Presets
Get started instantly with
--preset=classic,--preset=github, or--preset=gitlab.Configurable Merge Strategies
Choose between merge, rebase, or squash strategies per branch type, with a three-layer configuration hierarchy (branch defaults → command overrides → CLI flags).
Robust Conflict Resolution
A state machine-based finish operation with
--continueand--abortsupport, so you never lose progress during complex merges.Hooks & Filters System
Customize operations with pre/post hooks and version/tag-message filters. Fully compatible with existing git-flow-avh hook scripts.
Custom Merge Messages
Use
--merge-messageand--update-messagewith placeholder support (%b,%p) for teams using commit message conventions like conventional commits.Configuration Scoping
Store config at repository, user, or system level with
--local,--global,--system, or--fileoptions on init.Install
Or download from the Releases page.
Links
We'd love for you to try it out! Report bugs, request features, or join the conversation right here on GitHub.
Beta Was this translation helpful? Give feedback.
All reactions