Understanding Common Git Workflows: Centralized, Feature Branch, Gitflow, and Forking

Today I share some Git usage experience from Tencent engineers.

1. Introduction

Developers inevitably use version‑control tools such as SVN or Git; the article briefly mentions the pain of SVN and the advantages of Git, such as fast cloning and powerful branching.

2. Centralized Workflow

The centralized workflow mirrors SVN: a central repository with developers committing directly after resolving conflicts. Git adds a local repository copy for each developer. Images illustrate the central repository and a sample commit log.

Key points: presence of a local repo, default branch name (master), and using Git commands instead of SVN commands.

3. Feature‑Branch Workflow

Based on the centralized model, each feature is developed on its own descriptive branch (e.g., feat‑personal‑page , issue‑#1702 ). After development, a pull request (PR) merges the feature branch into master , enabling code review and discussion.

Images show a typical PR view and the cleaner commit history compared with the centralized approach.

4. Gitflow Workflow

Gitflow defines a strict branching model with long‑living master and dev branches, plus supporting branches for features, releases, hotfixes, and tags. The article walks through creating a feature branch from dev , merging via PR, handling hotfixes from a tagged release, and final release branching.

Several diagrams illustrate the branch structure and the release process.

5. Forking Workflow

Common in open‑source projects, forking creates a personal copy of a remote repository. Contributors develop in their fork, then submit a PR to the original repository. The article explains the fork operation and the PR flow with illustrative images.

6. Summary

Centralized workflow is the foundation and easy for SVN users to adopt. Feature‑branch workflow adds isolation and PR‑based review. Gitflow suits large, fast‑moving projects with a strict model. Forking is ideal for open‑source contributions. Teams should choose or adapt a workflow that fits their context.