Help Center/ CodeArts Repo/ User Guide/ New Version (Recommended)/ More About Git/ Git Workflows/ Branch Development Workflow
Updated on 2023-07-25 GMT+08:00
View PDF
Share

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.

Parent topic: Git Workflows