git-flow mit Homebrew installieren

Projektlinks

• Homepage

Befehle und Aliase

• git-flow

Projektgeschichte

Driessen published the branching model on January 5, 2010 and opened the gitflow repository later that month. The model organized release-oriented development around long-lived master and develop branches plus short-lived feature, release, and hotfix branches. The command package encoded that procedure as `git flow init`, `git flow feature`, `git flow release`, `git flow hotfix`, and related subcommands.

Adoptionsgeschichte

The model became one of the most recognizable Git workflow patterns of the 2010s. Driessen's 2020 reflection says many software teams treated git-flow almost like a standard, while also cautioning that continuously delivered web applications often benefit from simpler workflows such as GitHub Flow. The original repository's README later thanked users for more than fifteen years of adoption and pointed to git-flow-next as the maintained successor.

Wie es verwendet wird

Practitioners used git-flow to initialize branch naming conventions, start feature branches from develop, finish them back into develop, prepare release branches, and apply urgent fixes from master through hotfix branches. The CLI wrapped ordinary Git branch, merge, tag, publish, and pull operations into named release-management steps.

Warum Paket-Nerds sich dafür interessieren

git-flow is significant in package-manager culture because it turned a blog-post workflow into an installable Git extension. Its formulae and distro packages made `git flow` a standard command on developer machines, even as later teams debated whether the workflow fit CI/CD-heavy projects.

Zeitleiste

• 2010: Driessen published the successful Git branching model.
• 2010: The gitflow repository began and early 0.x releases followed.
• 2020: Driessen added a reflection warning against dogmatic use for continuous-delivery web applications.
• 2025: The original repository marked git-flow-next as the maintained successor.

Related projects

• git-flow influenced git-flow-avh, git-flow-completion, Tower's Git-flow integration, and git-flow-next.

Quellen

• https://git-flow.sh/blog/posts/how-git-flow-next-improves-upon-git-flow-avh/
• https://github.com/bobthecow/git-flow-completion
• https://github.com/nvie/gitflow
• https://github.com/nvie/gitflow#readme
• https://nvie.com/posts/a-successful-git-branching-model/