# Install git-flow with Homebrew

Extensions to follow Vincent Driessen's branching model. Version 0.4.1 via Homebrew; verified from local package data.

## Install

```sh
sudo av install brew:git-flow
```

Additional install commands:

### macOS

- Homebrew (100%):

```sh
brew install git-flow
```

  Evidence: provider-native install command

## Package facts

- **Package key:** brew:git-flow
- **Package manager:** Homebrew
- **Version:** 0.4.1
- **Source summary:** Extensions to follow Vincent Driessen's branching model
- **Homepage:** <https://github.com/nvie/gitflow>
- **Repository:** <https://github.com/nvie/gitflow>
- **Generated:** 2026-08-03T00:40:33+00:00

## Executables

- git-flow (alias)

## Install behavior

- Bottle: not available

## Freshness

- Page generated: 2026-08-03
- Package-manager version: 0.4.1
## Project history and usage

git-flow is the original command-line extension package for Vincent Driessen's Git branching model, providing high-level commands for feature, release, hotfix, and support branches.

### Project history

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.

### Adoption history

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.

### How it is used

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.

### Why package nerds care

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.

### Timeline

- 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.

### Sources

- <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/>


## Security Notes

narrow executable package without higher-risk signals.

- **Geiger risk:** green / low
- narrow executable package without higher-risk signals


## Combined YAML source

View the package source record on GitHub. [combined/git-flow.yml](https://github.com/automic-vault/db/blob/main/combined/git-flow.yml)


## Sources

- Nucleus package database
- Geiger risk classifier
- curated package history
- pkgdb category and tag curation