git branch strategy

In actual development, we should follow several basic principles for branch management:

First of all, the masterbranch should be very stable, that is, it is only used to release new versions, and usually cannot work on it ;

Where do you work? All work is done on the devbranch, that is to say, the devbranch is unstable. At a certain time, such as when the 1.0 version is released, the devbranch will be merged to the masterabove , and the master1.0 version will be released on the branch;

Each of you and your friends devis working on the branch, and everyone has their own branch, and devit is enough to merge into the branch from time to time.

So, the teamwork branch looks like this:

git-br-policy

Guess you like

Origin http://43.154.161.224:23101/article/api/json?id=324838541&siteId=291194637