# Git Flow

> A way to use branches. It has main, develop, feature, release and hotfix branches.

**Field:** Software Development  
**Category:** Version Control  
**Also known as:** Gitflow, git-flow, GitFlow Workflow

## Think of it like

Think of it like a busy kitchen with stations. Food moves from prep, to the cook, to the pass, in a set order.

## Definition

Git Flow is a branching strategy with two long-lived branches and three short kinds. Main holds what is live, and develop holds the next release. Feature branches come off develop and merge back to it. A release branch moves develop into main. A hotfix branch fixes main fast and is merged into both.

## Example

Lucy's team ships an app every three months. They use Git Flow, with a release branch for each version.

## Why it matters

It suits apps shipped in versions. Each release can be kept apart and fixed on its own.

## Common mistake

Using Git Flow for a website shipped many times a day. Its author suggests something simpler for that.

## Three principles

- **Two long branches.** Main and develop live on.
- **Three short kinds.** Feature, release and hotfix.
- **Made for versions.** Best for planned releases.

## Related terms

- [Branching Strategy](https://learn.benibix.com/term/development/branching-strategy)
- [Trunk-Based Development](https://learn.benibix.com/term/development/trunk-based-development)
- [Feature Branch](https://learn.benibix.com/term/development/feature-branch)
- [Git Tag](https://learn.benibix.com/term/development/git-tag)
- [Semantic Versioning (SemVer)](https://learn.benibix.com/term/development/semantic-versioning)

## Taught in

- [Git Branching Strategies](https://learn.benibix.com/learn/development-version-control/git-branching-strategies): Git and GitHub, 13/13

![Two panels. Trunk-based development, lit up: one main line with many tiny branches that each rejoin it within a day. Git Flow: five lines, main, develop, feature, release and hotfix. Features join develop, a release branch moves develop into main, and a hotfix goes straight from main back into both. A note says fewer, shorter branches mean fewer merge conflicts.](https://learn.benibix.com/diagrams/dev3-git-workflows.svg)

---

Source: https://learn.benibix.com/term/development/git-flow
Author: Behnia Zarei (a developer in Vienna, Austria, who builds and teaches data, AI and business intelligence at BENIBIX)
Publisher: BENIBIX Learn (https://learn.benibix.com/)
Last updated: 2026-11-17
Licence: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Quote freely with attribution.
