Visitar URL original
git-flow-next 2.1 makes worktrees a first-class part of the workflow, so switching branches means changing directories instead of stashing. Windows binaries are now signed, too.
git-flow-next 2.0 introduces shared, committable configuration via a .gitflow file, tab completion for both command forms, and a stricter, safer foundation across the board.
The honest 13-month journey of building git-flow-next with AI — what worked, what failed, and why the guidelines turned out to be the real product.
git-flow-next 1.0 is here with full git-flow and git-flow-avh compatibility, customizable branch configuration, seamless migration, and an exciting roadmap ahead.
Discover how git-flow-next modernizes Git Flow with flexible branch dependencies, customizable workflows, and active maintenance for todays development teams.
How separate merges into "main" and "develop" can lead to history fragmentation, merge conflicts, and sync issues with the classic git-flow approach.
Learn how git-flow-avh improves upon the original git-flow model, offering more flexibility, better release management, and increased configurability.