api: YAML JSON TOON Database version: 1.0.0 format: toon dataset: id: 2514 slug: version-control-workflows title: Version Control Workflows description: Common branching and collaboration workflows. summary: "Branching and collaboration workflows for version control: centralized, feature branch, Gitflow, forking and trunk-based development, plus GitHub Flow, GitLab Flow, release branching and stacked changes. Each row says how work moves from a branch to release." use_when[2]: You are choosing or documenting a team's branching strategy.,You need to compare workflows by release cadence and review style. caveats[2]: "The right workflow depends on release cadence, team size and test automation; there is no universal best.","Several names are used loosely, and tools differ in how they implement the same workflow." related[3]: git-essential-commands,cicd-pipeline-stages,site-reliability-practices entry_count: 9 fields[2]{section,field,type,example}: data,workflow,string,Centralized data,description,string,All developers commit to a single shared branch. category: DevOps category_slug: devops tags: "devops,git,workflow" view_count: 43 created_at: 1792832553 updated_at: 1792832553 data[9]{workflow,description}: Centralized,All developers commit to a single shared branch. Feature Branch,Each feature is developed in an isolated branch and merged via pull request. Gitflow,"Uses master, develop, feature, release, and hotfix branches." Forking,Contributors fork the repository and submit pull requests. Trunk-Based,Developers commit to a single trunk frequently with short-lived branches. GitHub Flow,"Short-lived branches off main, pull requests for review, merge and deploy continuously." GitLab Flow,Feature branches plus environment or release branches to model staged deployment. Release Branching,Cut a branch per release for stabilization and patching while main continues forward. Stacked Changes,Break a large change into a chain of small dependent branches reviewed and merged in order.