GitWorkflows
GitWorkflows refer to the conventions teams use to manage changes in a Git repository. A workflow defines how branches are created and used, how changes are proposed and reviewed, and how and when code is integrated and released. Core concepts include branches, commits, merges, pull requests, and continuous integration.
- Centralized workflow: A single main integration branch is used, and developers push to a shared repository.
- Feature branch workflow: Each feature or bug fix is developed in its own branch off the main
- Git Flow: A structured model with long-running branches such as main, develop, feature/*, release/*, and hotfix/*.
- GitHub Flow: A lightweight variant where main is deployable at all times. Developers create short-lived branches
- Forking workflow: Common in open source. Contributors fork the repository, push changes to their own fork,
- Trunk-based development: Developers integrate frequently into a single trunk (often main) with very short-lived or no
Choosing a workflow depends on team size, release cadence, code ownership, and tooling. Larger teams with formal