-
Notifications
You must be signed in to change notification settings - Fork 635
Drop git flow
#648
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Drop git flow
#648
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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]>
Member
Author
|
/updpkgsums The workflow run was started. |
Signed-off-by: Johannes Schindelin <[email protected]>
mjcheetham
approved these changes
Oct 15, 2025
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
This was referenced Oct 16, 2025
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
4 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
gitflowrepository 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-nextis 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.