Deze pagina is nog niet beschikbaar in uw eigen taal. We werken er hard aan om meer taalversies toe te voegen. Bedankt voor uw steun.

On this page

Branch Development Workflow

Updated on 2023-12-04 GMT+08:00

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

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback