Workflow Overview
Git workflows can be used for versioning, project process management, and collaborative development, improving project management and collaborative development capabilities. It is necessary to pick your own Git workflow based on your team requirements and workflow for continuous integration, continuous delivery, and fast iteration.
The table below compares core concepts, branch complexity, and suggestions on selection for various workflows to help you choose the one that best fits your needs.
| Workflow | Working on a centralized workflow | Git Flow | Feature branch workflow |
|---|---|---|---|
| Core Concept | Development centered around a single repository. Developers clone the code and push changes directly. | Fixed branch types with predefined transition rules. | Independent development on branches created from and merged into the main branch. |
| Branch Complexity | Low (only the main branch) | High (five branch types) | Medium (main branch + feature branches) |
| Suggestions on Selection | Small teams (three to five members) or short-term projects | Medium-to-large projects with long iteration cycles and multi-role collaboration | Medium-sized teams requiring parallel development and rapid iteration |
What is your overall rating for this page?
Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot
