nvie/gitflow
Git extensions to provide high-level repository operations for Vincent Driessen's branching model. observed · 2026-08-28
Health v2 · maintenance only
10/100
- Activity 47
- Release rhythm 35
- Longevity 100
Flags: no_releases archived no_license no_readme
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.
- gap_med: n/a
- age_days: 6069
- days_rel: n/a
- days_push: 323
- n_releases_24m: 0
Adoption not part of the score
26792 stars · 2619 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-29, confidence not recorded
Git extensions implementing Vincent Driessen's git-flow branching model as high-level repository operations. Written in Shell, it automates creating and managing feature, release, and hotfix branches.
Use cases
- manage feature, release, and hotfix branches in git
- adopt the git-flow branching model
- automate release branch creation and merging
- support multiple versioned releases of software
- standardize team git workflow
When to choose
- your team releases explicitly versioned software
- you need to support multiple versions in the wild
- you want a well-known, battle-tested branching workflow
When to avoid
- your team does continuous delivery (prefer GitHub flow)
- you want a lightweight single-branch workflow
- you need actively developed features
Facets
cli-tool · maturity maintenance
version-control cli developer-tools version-control developer-tools cli cross-platform git-flow branching-model git-extensions shell command-line
2 sources
- homepage: http://nvie.com/posts/a-successful-git-branching-model/ · fetched 2026-08-29 · f48eccc0573c
- site_page: https://nvie.com/about · fetched 2026-08-29 · 72f699800633
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| nvie/gitflow | main | 10 |
For agents
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem