- Learning Continuous Integration with Jenkins(Second Edition)
- Nikhil Pathania
- 148字
- 2021-07-02 21:18:31
Branching strategy
When using a Version Control System, keep the branching to a minimum. A few companies have only one main branch, and all the development activity happens on that. Nevertheless, most of the companies follow some branching strategies. This is because there is always a possibility that a part of the team may work on one release, while others may work on another release. Other times, there is a need to support the older release versions. Such scenarios always lead companies to use multiple branches.
GitFlow is another way of managing your code using multiple branches. In the following method, the Master/Production branch is kept clean and contains only the releasable, ready-to-ship code. All the development happens on the Feature branches, with the Integration branch serving as a common place to integrate all the features. The following diagram is a moderate version of the GitFlow:
Branching strategy
- 操作系統實用教程(Linux版)
- Social Media Mining with R
- Mobile-first Bootstrap
- Learning Magento 2 Administration
- μC/OS-III內核實現與應用開發實戰指南:基于STM32
- 大規模分布式系統架構與設計實戰
- OpenStack Essentials(Second Edition)
- OpenHarmony開發與實踐:基于紅莓RK2206開發板
- Angular權威教程
- Windows Azure實戰
- Python機器學習系統構建(原書第3版)
- 用“芯”探核:基于龍芯的Linux內核探索解析
- 從零開始學Windows 7
- Linux系統編程
- 計算機操作系統實用教程