Question

A small startup team is adopting a formal collaboration workflow for the first time. They want a simple, branch-based process that supports continuous deployment and quick iteration, without the overhead of long-lived release branches or complex versioning stages. Which workflow best matches these goals?

Accepted Answer

GitHub Flow, a lightweight branch-based workflow centered on short-lived feature branches and pull requests

Answer

Gitflow, which uses long-lived develop, release, and hotfix branches for scheduled releases

Answer

A trunk-only workflow where everyone commits directly to main with no branches or reviews

Answer

A forking-only workflow where each developer maintains a separate copy and never merges back