# git-flow を Homebrew, apk, apt, MacPorts, winget でインストール

git-flow のインストール経路、実行ファイル、メタデータ、AI エージェント向けセキュリティノートを確認します。

## インストール

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

追加のインストールコマンド:

### macOS

- Homebrew (100%):

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

  証拠: local Homebrew formula metadata

- MacPorts (94%):

```sh
sudo port install git-flow
```

  証拠: MacPorts ports tree: devel/git-flow/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1

### Linux

- apk (92%):

```sh
sudo apk add git-flow
```

  証拠: Alpine Linux edge package indexes: git-flow from https://dl-cdn.alpinelinux.org/alpine/edge/community/x86_64/APKINDEX.tar.gz

- Debian apt (92%):

```sh
sudo apt install git-flow
```

  証拠: Debian stable package indexes: git-flow from https://deb.debian.org/debian/dists/stable/main/binary-amd64/Packages.xz

### Windows

- winget (92%):

```sh
winget install --id GitTower.GitFlowNext -e
```

  証拠: Windows Package Manager source index: GitTower.GitFlowNext from https://cdn.winget.microsoft.com/cache/source.msix

## パッケージ情報

- **パッケージキー:** brew:git-flow
- **パッケージマネージャ:** Homebrew
- **バージョン:** 0.4.1
- **ソース概要:** Extensions to follow Vincent Driessen's branching model
- **ホームページ:** <https://github.com/nvie/gitflow>
- **リポジトリ:** <https://github.com/nvie/gitflow>
- **生成日時:** 2026-08-03T19:37:03+00:00

## 実行可能ファイル

- git-flow (エイリアス)

## インストール挙動

- Bottle: 利用不可

## バージョンと鮮度

- ページ生成日: 2026-08-03
- マネージャ版: 0.4.1
## プロジェクトの歴史と使われ方

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.

### プロジェクトの歴史

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.

### 採用の歴史

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.

### 使われ方

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.

### パッケージ好きにとっての重要性

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.

### タイムライン

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

### ソース

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


## セキュリティノート

narrow executable package without higher-risk signals.

- **Geiger リスク:** グリーン / 低
- narrow executable package without higher-risk signals

## 他のパッケージマネージャ記録

- Debian apt - git-flow - 1.12.3-3: normalized package name match | Debian stable package indexes: git-flow from https://deb.debian.org/debian/dists/stable/main/binary-amd64/Packages.xz | Git extension to provide a high-level branching model | https://github.com/petervanderdoes/gitflow/wiki
- Ubuntu apt - git-flow - 1.12.3-3: normalized package name match | Ubuntu 24.04 LTS package indexes: git-flow from https://archive.ubuntu.com/ubuntu/dists/noble/universe/binary-amd64/Packages.gz | Git extension to provide a high-level branching model | https://github.com/petervanderdoes/gitflow/wiki
- apk - git-flow - 1.12.3-r1: normalized package name match | Alpine Linux edge package indexes: git-flow from https://dl-cdn.alpinelinux.org/alpine/edge/community/x86_64/APKINDEX.tar.gz | Git extension to provide a high-level branching model | https://github.com/petervanderdoes/gitflow-avh
- apk - git-flow-doc - 1.12.3-r1: normalized package name match | Alpine Linux edge package indexes: git-flow-doc from https://dl-cdn.alpinelinux.org/alpine/edge/community/x86_64/APKINDEX.tar.gz | Git extension to provide a high-level branching model (documentation) | https://github.com/petervanderdoes/gitflow-avh
- MacPorts - git-flow: normalized package name match | MacPorts ports tree: devel/git-flow/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1
- winget - GitTower.GitFlowNext: normalized package name match | Windows Package Manager source index: GitTower.GitFlowNext from https://cdn.winget.microsoft.com/cache/source.msix


## Combined YAML source

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


## ソース

- pkg.so package database
- Geiger risk classifier
- curated package history
- pkgdb category and tag curation
- external package-manager database matches
- cross-ecosystem install command graph