Changelog

[2.0.0] - 2026-08-09

Added

Shared, committable configuration: init --shared writes the git-flow setup to a .gitflow file at the repository root and copies it into local config, so a team's branch model can live in the repository instead of every clone
--shared on every config add, edit, rename, and delete verb edits the shared .gitflow file and re-syncs local config
config sync copies .gitflow into local config, and config status reports drift between the two (exit code 6 when they differ)
A fresh clone carrying a .gitflow is offered activation on first run — prompted when interactive, applied automatically with gitflow.shared.autoInit, and topic branch types declared only in the shared file get working commands before activation
Shell tab completion for both the git-flow and git flow invocations, covering bash, zsh, and fish
init --init creates the repository when run outside one, with an interactive prompt offering the same when the flag is absent; the new repository's initial branch is the resolved git-flow trunk rather than init.defaultBranch

Changed

Breaking: git flow version now prints 2.0.0 (git-flow-next) instead of git-flow-next version 2.0.0, so the first whitespace-separated token is a bare version number as tooling written against git-flow-avh expects. Scripts matching the old string must be updated
Release archives now contain a plain git-flow / git-flow.exe binary instead of a version- and platform-suffixed filename, so it works as the git flow subcommand without renaming after extraction

Fixed

Boolean git-config values now follow git-config(1) rules: yes, on, and non-zero integers are truthy and matching is case-insensitive. Previously only the literal true counted, so a setting like git config gitflow.release.finish.push yes was silently a no-op
config edit no longer resets boolean settings that were not passed, so editing one field can no longer silently clear an unrelated one such as autoUpdate
Interactive init now stores entered branch prefixes verbatim instead of appending a slash, so answering feature_ produces feature_login rather than feature_/login
Hooks and filters run from a linked worktree now resolve a relative gitflow.path.hooks or core.hooksPath against that worktree and execute with it as their working directory, instead of pointing at the main checkout
Commands run outside a git repository now report a git error suggesting git init (exit code 3) instead of a git-flow-not-initialized error steering to git flow init
Adding a base branch now rolls back its saved configuration when creating the git branch fails, leaving no orphaned config and keeping the command safe to retry
The config command group is no longer preempted by first-run shared-config activation, including its nested add, edit, rename, and delete subcommands
--shared edits now warn when an untrusted gitflow.path.hooks is withheld from local config, matching what config sync already reported
Declining the "create a repository?" prompt now reports a decline instead of an internal probe failure
git-flow-next now builds on every Go target OS; terminal detection previously had no implementation for aix, solaris, illumos, and plan9

[1.2.0] - 2026-08-01

Added

git flow integrate command to merge changes from a parent branch into a topic branch, with options resolved from an integrate config namespace
finish now pushes the finished branches and release tag to the remote after merging, honoring push options
update --continue and update --abort to resume or cancel an update interrupted by conflicts
finish now detects and auto-clears stale merge state left by a previous interrupted operation
delete now fetches and runs a remote sync-check before deleting a branch (--fetch, gitflow.<type>.delete.fetch)
start can derive the branch name from a configured version filter
Windows arm64 build target

Changed

finish now runs a stricter pre-merge sync check: it aborts when the parent (merge-target) branch or the topic branch is behind or has diverged from its remote (with a diverged-specific message), while tolerating either being ahead; --force skips the check
finish now treats a fetch failure against a reachable-but-failing remote as fatal (was a silent note); the error names the cause and suggests --no-fetch / --force
start now fetches by default before creating a branch (skipped silently when no remote is configured); disable with --no-fetch or gitflow.<type>.start.fetch false. Shares the unified fetch resolution (default → config → flag) with finish
Commands now refuse to act on merge state owned by a foreign operation and on structurally-incomplete state, returning exit code 3 instead of proceeding destructively

Fixed

init now fails fast when the git user identity is missing
Branch names are validated with git check-ref-format, and dots are now allowed in base branch names
Branch names are resolved case-insensitively while preserving their original case
Leaf commands now reject unexpected positional arguments
delete, rename, and finish are gated when git-flow is uninitialized
Base-branch config cleanup is scoped to local config and treats a missing key as a no-op
finish --abort is a no-op when no merge is in progress
Hooks and filters now run on Windows (executed via sh)

[1.1.0] - 2026-04-06

Added

Push-option support for publish command (--push-option / -o)
Support for configurable hooks directory via gitflow.path.hooks and core.hooksPath

Fixed

Validate remote exists before any state-changing delete operations
Validate remote before remote operations (publish, track, finish sync)
Check if remote exists before attempting to delete remote branch
Skip fetch when no remote is configured
Use empty commit instead of README.md when initializing empty repositories
Default to empty version tag prefix during init
Thread config correctly into tag creation step during finish

[1.0.0] - 2026-02-08

Added

--no-verify option for finish command to skip git hooks during merge
--merge-message and --update-message options 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)
--force option 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 true for 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 publish command for topic branches to push branches to remote
Add --squash-message option 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 publish command (was returning "not implemented")
Fix git flow <type> finish to allow optional branch name (uses current branch)

[0.2.0] - 2026-01-11

Added

Add track command for topic branches to track existing remote branches
Add --fetch option 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