Skip to content

Conversation

@dscho
Copy link
Member

@dscho dscho commented Oct 14, 2025

I dearly regret ever adding Git Flow to Git for Windows. Not only did the entire flow strike me as counterproductively complex, the project itself was apparently not very successful in applying its own flow and went super stale.

We even tried to switch to a fork (hoping against hope that it was temporary). But even that fork was archived over two years ago.

Today, as a very belated sign that its maintainer is still alive, the gitflow repository was archived.

There was that recommendation to switch to git-flow-next. But I think we'd be better served, for various reasons. Most importantly:

  • Git Flow seems quite unloved (and I understand why). We haven't heard much in the way of requests to update it. So I'll just go ahead and assume that there are 0 users left.
  • git-flow-next is written in Go, and therefore its executable is multiple megabytes large, much larger than the Bash scripts of the original version. I am not willing to force every Git for Windows user to pay that extra cost, certainly not for something like Git Flow.

dscho added 2 commits October 14, 2025 14:11
After the "successful" strategy has languished for many years, and after
even a "temporary fork" https://github.com/petervanderdoes/gitflow-avh
(that Git for Windows was forced to switch to) has been archived for
more than two years, even the original repository was archived, as per
nvie/gitflow#3 (comment), at
_very_ long last.

Vincent Driessen recommends switching to `git-flow-next`, which is
written in Go, and which I am unwilling to distribute with Git for
Windows because 1) it would increase the installer size noticeably, and
2) that strategy seems not to be quite as successful as claimed, given
the low usage numbers.

So let's drop it.

Since there has not been a whole lot of talk about the staleness of `git
flow`, it is safe to assume that there are few users left, if any.
Therefore, I deem a deprecation period unnecessary.

Signed-off-by: Johannes Schindelin <[email protected]>
That project has gone super stale over the past seven or so years.

Signed-off-by: Johannes Schindelin <[email protected]>
@dscho
Copy link
Member Author

dscho commented Oct 14, 2025

/updpkgsums

The workflow run was started.

Signed-off-by: Johannes Schindelin <[email protected]>
@dscho dscho merged commit f6cea7b into main Oct 15, 2025
22 checks passed
@dscho dscho deleted the drop-git-flow branch October 15, 2025 20:09
gitforwindowshelper bot pushed a commit to git-for-windows/git-sdk-arm64 that referenced this pull request Oct 16, 2025
The Git Flow package is obsolete and unmaintained. It is no longer distributed with Git for Windows, see git-for-windows/build-extra#648 for details.

checking dependencies...

Packages (1) git-flow-1.12.3-2

Total Removed Size:  0.22 MiB

:: Do you want to remove these packages? [Y/n]
:: Processing package changes...
removing git-flow...
gitforwindowshelper bot pushed a commit to git-for-windows/git-sdk-32 that referenced this pull request Oct 16, 2025
The Git Flow package is obsolete and unmaintained. It is no longer distributed with Git for Windows, see git-for-windows/build-extra#648 for details.

Here is the output of the command that was run in
https://github.com/git-for-windows/git-for-windows-automation/actions/runs/18565589197:

+ set -x
+ pacman -Rns --noconfirm git-flow
checking dependencies...

Packages (1) git-flow-1.12.3-2

Total Removed Size:  0.22 MiB

:: Do you want to remove these packages? [Y/n]
:: Processing package changes...
removing git-flow...
+ echo 0
gitforwindowshelper bot pushed a commit to git-for-windows/git-sdk-64 that referenced this pull request Oct 16, 2025
The Git Flow package is obsolete and unmaintained. It is no longer distributed with Git for Windows, see git-for-windows/build-extra#648 for details.

Here is the output of the command that was run in
https://github.com/git-for-windows/git-for-windows-automation/actions/runs/18565589197:

+ set -x
+ pacman -Rns --noconfirm git-flow
checking dependencies...

Packages (1) git-flow-1.12.3-2

Total Removed Size:  0.22 MiB

:: Do you want to remove these packages? [Y/n]
:: Processing package changes...
removing git-flow...
+ echo 0
gitforwindowshelper bot pushed a commit to git-for-windows/git-sdk-arm64 that referenced this pull request Oct 16, 2025
The Git Flow package is obsolete and unmaintained. It is no longer distributed with Git for Windows, see git-for-windows/build-extra#648 for details.

Here is the output of the command that was run in
https://github.com/git-for-windows/git-for-windows-automation/actions/runs/18565589197:

+ set -x
+ pacman -Rns --noconfirm git-flow
checking dependencies...

Packages (1) git-flow-1.12.3-2

Total Removed Size:  0.22 MiB

:: Do you want to remove these packages? [Y/n]
:: Processing package changes...
removing git-flow...
+ echo 0
dscho added a commit to git-for-windows/git-sdk-arm64 that referenced this pull request Oct 16, 2025
The Git Flow package is obsolete and unmaintained. It is no longer
distributed with Git for Windows, see
git-for-windows/build-extra#648 for details.

Here is the output of the command that was run in

https://github.com/git-for-windows/git-for-windows-automation/actions/runs/18565589197:

+ set -x
+ pacman -Rns --noconfirm git-flow
checking dependencies...

Packages (1) git-flow-1.12.3-2

Total Removed Size:  0.22 MiB

:: Do you want to remove these packages? [Y/n]
:: Processing package changes...
removing git-flow...
+ echo 0
nagromc added a commit to nagromc/dotfiles that referenced this pull request Oct 20, 2025
Git Flow has bee removed from Git for Windows.
See git-for-windows/build-extra#648
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants