Git Flow not recognized after 2.51.0.windows.1

[thos25]

Existing issues matching what you're seeing

• I was not able to find an open or closed issue matching what I'm seeing

Git for Windows version

$ git --version --build-options
git version 2.51.2.windows.1
cpu: x86_64
built from commit: bd2ecbae58213046a468256b95fc4864de25bdf5
sizeof-long: 4
sizeof-size_t: 8
shell-path: D:/git-sdk-64-build-installers/usr/bin/sh
feature: fsmonitor--daemon
libcurl: 8.16.0
OpenSSL: OpenSSL 3.5.4 30 Sep 2025
zlib: 1.3.1
SHA-1: SHA1_DC
SHA-256: SHA256_BLK
default-ref-format: files
default-hash: sha1

Windows version

Windows 10

Windows CPU architecture

x86_64 (64-bit)

Additional Windows version information

Microsoft Windows [Version 10.0.19045.6456]

Options set during installation

Chose the defaults

Other interesting things

No response

Terminal/shell

Powershell

Commands that trigger the issue

Any `git flow` commands trigger the issue.  For example:

git flow init -d
git: 'flow' is not a git command. See 'git --help'.

The most similar commands are
        reflog
        show

Expected behaviour

Expected behavior is git flow runs and initializes a project.

Actual behaviour

Receive the following errpr:

git flow init -d
git: 'flow' is not a git command. See 'git --help'.

The most similar commands are
reflog
show

Repository

No response

[thos25]

Downgrading to git 2.51.0.windows.1 seems to restore this functionality

[dscho]

Git Flow was dropped from Git for Windows as of version v2.51.1 because it has not been maintained in years (even the original repository was finally archived, at long last, after not responding to any issues for almost a decade), see git-for-windows/build-extra@8baf99f.

The best I can do for you is to suggest to switch to git-flow-next, which seems to be maintained. It will require some changes in your process because the command you will need to call is naturally not git flow, but git flow-next instead.

[bmcdonnell-fb]

Dupe of #5901.

[NETSphereSoft]

Look at #5901 (comment) for a possible solution.

[azadmoon]

ok

[mdcc7844-art]

#6017 #6017

[bmcdonnell-fb]

Duplicate of #5957

Not it isn't. It doesn't even make sense for an issue (such as this) to be a dupe of a PR (5957).

Bot or spammer?