# Installer git-flow avec Homebrew, apk, apt, MacPorts, winget Consultez les chemins d'installation, exécutables, métadonnées et notes de sécurité de git-flow pour les workflows d'agents IA. ## installation ```sh sudo av install brew:git-flow ``` Commandes d'installation supplémentaires: ### macOS - Homebrew (100%): ```sh brew install git-flow ``` Preuve: local Homebrew formula metadata - MacPorts (94%): ```sh sudo port install git-flow ``` Preuve: 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 ``` Preuve: 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 ``` Preuve: 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 ``` Preuve: Windows Package Manager source index: GitTower.GitFlowNext from https://cdn.winget.microsoft.com/cache/source.msix ## Faits du paquet - **Clé du paquet:** brew:git-flow - **Gestionnaire de paquets:** Homebrew - **Version:** 0.4.1 - **Résumé source:** Extensions to follow Vincent Driessen's branching model - **Page d'accueil:** - **Dépôt:** - **Généré:** 2026-08-03T19:37:03+00:00 ## exécutables - git-flow (alias) ## Comportement d'installation - Bouteille: non disponible ## Version et fraîcheur - page générée: 2026-08-03 - version du gestionnaire: 0.4.1 ## Historique du projet et usages 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. ### Historique du projet 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. ### Historique d'adoption 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. ### Modes d'utilisation 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. ### Pourquoi les passionnés de paquets s'y intéressent 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. ### Chronologie - 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 - - - - - ## Notes de sécurité narrow executable package without higher-risk signals. - **Risque Geiger:** vert / faible - narrow executable package without higher-risk signals ## Autres enregistrements de gestionnaires de paquets - 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) ## Sources - 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