v1.2.0
Added
git flow integratecommand to merge changes from a parent branch into a topic branch, with options resolved from anintegrateconfig namespacefinishnow pushes the finished branches and release tag to the remote after merging, honoring push optionsupdate --continueandupdate --abortto resume or cancel an update interrupted by conflictsfinishnow detects and auto-clears stale merge state left by a previous interrupted operationdeletenow fetches and runs a remote sync-check before deleting a branch (--fetch,gitflow.<type>.delete.fetch)startcan derive the branch name from a configured version filter- Windows arm64 build target
Changed
finishnow 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;--forceskips the checkfinishnow 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/--forcestartnow fetches by default before creating a branch (skipped silently when no remote is configured); disable with--no-fetchorgitflow.<type>.start.fetch false. Shares the unified fetch resolution (default → config → flag) withfinish- 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
initnow 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, andfinishare 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 --abortis a no-op when no merge is in progress- Hooks and filters now run on Windows (executed via
sh)
Installation
See the installation instructions in the README.
Checksums
SHA-256 checksums for the release artifacts are available in the checksums.txt file.