If you have a small team and work together, using github pull is a bit expensive,
You can definitely use one of the following methods:

• Review locally, submit to develop branch after passing, and release to master at the right time
• Submit directly to the devlop branch. If it is not suitable, revert it back. This may cause some trouble
• Everyone maintains his or her own branch, and then a dedicated person merges it into develop

In this way, you can also use other functions such as github issues.

Using sourcetree’s git workflow is very convenient~~~

I will answer it myself

git flow

The above is a relatively classic git flow

Still looking for information about forking workflow

Let’s talk about how we currently use git branches

The overall project is divided into two branches: master and develop. Master is mainly used to publish websites. develop is mainly used for separate use.
When everyone develops, they clone it from develop and create a developer's own branch, such as zhang. (When there are new joiners, use the same method to rename the branch li.). When the development work is completed, submit the local warehouse and git push your own branch. Finally, merge develop into your own branch (it may have been modified by the developer during development) to ensure that the merge is successful. After the merge is correct, merge the currently merged zhang branch into the develop branch. (Note: The merge operation here is first merged into the local branch. Then merged into the remote branch. It is a bit more than one step).
After the last day of work, develop will be merged into the master branch and run online through master.

In addition, when there are urgent bugs that need to be corrected in the online environment. Then create a branch from master. Independent maintenance. After that, synchronize the master and develop branches respectively.