From 550a5e3f5c6c6d49b4e537e28963efa60e5dd6cb Mon Sep 17 00:00:00 2001 From: Vincent Driessen Date: Tue, 14 Oct 2025 10:54:29 +0200 Subject: [PATCH 1/2] Announce git-flow-next --- README.mdown | 31 +++++++++++++++++++++++++++++++ 1 file changed, 31 insertions(+) diff --git a/README.mdown b/README.mdown index a01079b4b..cadd71ab7 100644 --- a/README.mdown +++ b/README.mdown @@ -1,3 +1,34 @@ +> [!IMPORTANT] +> +> # ⚠️ git-flow has moved to git-flow-next! +> +> **This repository is no longer maintained.** The wonderful team at [Tower](https://www.git-tower.com/) has created [**git-flow-next**](https://git-flow.sh) — a modern, fully customizable evolution of git-flow, built on a generic branch dependency model. It’s fully backward compatible with git-flow, open source, and actively maintained. +> +> ### Get started with git-flow-next: +> +> - **Website:** https://git-flow.sh +> - **GitHub:** https://github.com/gittower/git-flow-next +> - **Evolution Story:** Read about the journey from git-flow → git-flow-avh → git-flow-next in [their blog post](https://git-flow.sh/blog) +> +> ### Why git-flow-next? +> +> git-flow-next builds upon the foundation laid by the original git-flow, offering: +> +> - Full customization of branch names and workflow +> - Modern implementation with active maintenance +> - Backward compatibility with existing git-flow workflows +> - Upcoming features like stacked branches and topic branch syncing +> +> ### Thank you ❤️ +> +> To everyone who has used, contributed to, and supported git-flow over the past 15+ years — thank you! Your feedback, contributions, and adoption made git-flow one of the most widely-used Git workflow tools. Special thanks to Peter van der Does for maintaining git-flow-avh, and to the folks at Tower for carrying the torch forward with git-flow-next. + +--- + +(Below, you’ll find the original documentation for historical reference.) + +--- + git-flow ======== From d2eee63886e23c27a0c0418603c8264276a86340 Mon Sep 17 00:00:00 2001 From: Vincent Driessen Date: Tue, 14 Oct 2025 11:12:50 +0200 Subject: [PATCH 2/2] Clean up README by removing outdated sections --- README.mdown | 46 ---------------------------------------------- 1 file changed, 46 deletions(-) diff --git a/README.mdown b/README.mdown index cadd71ab7..b720b125e 100644 --- a/README.mdown +++ b/README.mdown @@ -71,37 +71,6 @@ See the [FAQ](http://github.com/nvie/gitflow/wiki/FAQ) section of the project Wiki. -Please help out ---------------- -This project is still under development. Feedback and suggestions are very -welcome and I encourage you to use the [Issues -list](http://github.com/nvie/gitflow/issues) on Github to provide that -feedback. - -Feel free to fork this repo and to commit your additions. For a list of all -contributors, please see the [AUTHORS](AUTHORS) file. - -Any questions, tips, or general discussion can be posted to our Google group: -[http://groups.google.com/group/gitflow-users](http://groups.google.com/group/gitflow-users) - -Contributing ------------- -Fork the repository. Then, run: - - git clone --recursive git@github.com:/gitflow.git - cd gitflow - git branch master origin/master - git flow init -d - git flow feature start - -Then, do work and commit your changes. **Hint**: ``export PATH=`pwd`:$PATH`` -from within the gitflow directory makes sure you're using the version of -gitflow you're currently developing. - - git flow feature publish - -When done, open a pull request to your feature branch. - License terms ------------- git-flow is published under the liberal terms of the BSD License, see the @@ -162,18 +131,3 @@ The ``-d`` flag will accept all defaults. git flow support start For support branches, the `` arg must be a commit on `master`. - - -Showing your appreciation -========================= -A few people already requested it, so now it's here: a Flattr button. - -Of course, the best way to show your appreciation for the original -[blog post](http://nvie.com/posts/a-successful-git-branching-model/) or the git-flow tool itself remains -contributing to the community. If you'd like to show your appreciation in -another way, however, consider Flattr'ing me: - -[![Flattr this][2]][1] - -[1]: http://flattr.com/thing/53771/git-flow -[2]: http://api.flattr.com/button/button-static-50x60.png