Branch Development Workflow
The core of the feature branch workflow is that every feature should be developed on a separate branch pulled off the master branch. This creates a work silo for every developer, ensures a stable master branch, and encourages team collaboration.
Process
Before developing a new feature, each developer should pull a new branch from the master branch and give it a descriptive name, for example, video-output or issue-#1061, to clearly state its purpose. By pushing local feature branches to the central repository, developers can share their code with each other without merging code into the master branch.
Advantages
- Developers can create merge requests to have their code reviewed before merge.
- Pushes to the master branch are less frequent.
Disadvantages
Only the master branch is used to incorporate changes. The instability of the branch is further increased in large-scale development projects.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.
