1 views collected around this technical thread.
This article explains how to design and evaluate a project's Git branching strategy by breaking branches into four hierarchical levels—feature, integration, production, and version‑sequence—using Git Flow as a concrete example to illustrate each level's purpose and typical branch patterns.
This article explains common Git branch types, including master, develop, feature, release, and hotfix branches, and details various continuous integration branch strategies such as Git Flow, GitHub Flow, and GitLab Flow, helping teams choose an appropriate branching model for efficient DevOps practices.
This article provides a comprehensive guide to GitLab code review, covering environment setup, Git flow basics, review methods, configuration of approvals, templates, issue linking, Code Quality integration with CI/CD, step‑by‑step practice, and recommendations for choosing between Community and Enterprise editions.
The article explains that selecting a Git branching model—Git‑flow, GitHub‑flow, or Gitlab‑flow—depends on a team's engineering capability and collaboration discipline rather than size, describing each model’s suitability, trade‑offs, and real‑world examples such as Facebook’s trunk‑based delivery.
This article explains three widely used Git workflows—Git flow, Github flow, and Gitlab flow—highlighting their feature‑driven development model, branch structures, step‑by‑step processes, advantages, drawbacks, and practical tips such as pull requests, protected branches, and commit squashing.