Centralized Workflow

• there is a single branch namedmaster where everyone syncs up to

Feature Branch Workflow

• is a logical extension of Centralized Workflow
• the core idea is that all feature development should take place in a dedicated branch instead of the master branch. This encapsulation makes it easy for multiple developers to work on a particular feature without disturbing the main codebase. It also means the master branch should never contain broken code, which is a huge advantage for continuous integration environments

Gitflow Workflow

• doesn’t add any new concepts or commands beyond what’s required for the Feature Branch Workflow. Instead, it assigns very specific roles to different branches and defines how and when they should interact
• https://nvie.com/posts/a-successful-git-branching-model/

GitHub Flow

• a simpler version of Gitflow Workflow, mainly built for those managing web apps
• https://guides.github.com/introduction/flow/

Trunk-Based Development

• https://trunkbaseddevelopment.com/

Simple Flow

• https://hackernoon.com/a-branching-and-releasing-strategy-that-fits-github-flow-be1b6c48eca2

Forking Workflow

• is fundamentally different than the other workflows
• instead of using a single server-side repository to act as the “central” codebase, it gives every developer a server-side repository. This means that each contributor has not one, but two repositories: a private local one and a public server-side one