Changelog
[1.0.0] - 2026-02-08
Added
--no-verifyoption for finish command to skip git hooks during merge--merge-messageand--update-messageoptions for finish command with placeholder support- Git config support for merge message options (
gitflow.<type>.finish.mergeMessage,gitflow.<type>.finish.updateMessage) - Configuration scope flags for init command (
--local,--global,--system,--file) --forceoption for init command to allow reconfiguration- Remote sync check before finish to ensure local branch is up-to-date with remote
Changed
- Default fetch behavior changed to
truefor finish command
Fixed
- Hooks now receive correct positional arguments
[0.3.0] - 2026-01-14
Added
- Add hooks and filters system for customizing git-flow operations
- Pre/post hooks for start, finish, publish, track, delete, and update actions
- Version filters for topic branches on start
- Tag message filters for topic branches that create tags on finish
- Add
publishcommand for topic branches to push branches to remote - Add
--squash-messageoption for custom squash commit messages on finish - Add config support for force deletion (
gitflow.branch.<type>.forceDelete)
Fixed
- Fix worktree support for hooks, filters, and merge state
- Fix shorthand
git flow publishcommand (was returning "not implemented") - Fix
git flow <type> finishto allow optional branch name (uses current branch)
[0.2.0] - 2026-01-11
Added
- Add
trackcommand for topic branches to track existing remote branches - Add
--fetchoption for topic branch finish command
Fixed
- Create base branches in dependency order during init
- Fix docs link in README.md
Changed
- Optimize binary size (~50% reduction)
[0.1.1] - 2025-09-24
Fixed
- Minor bug fixes and improvements
[0.1.0] - 2025-09-16
Added
- Initial release of git-flow-next
- Support for feature, release, hotfix, and support branch workflows
- Fully customizable base and topic branches with configurable prefixes and relationships
- Configurable merge strategies: merge, rebase, or squash when finishing branches
- Flexible configuration via git config or command-line flags
- Conflict recovery: resolve conflicts and continue where you left off
- Automatic updates to child branches (e.g., develop syncs from main)
- Compatibility with existing git-flow-avh repositories