1. Collaborative projects in the branch operation
2. spoke architecture for collaboration
3. Remote branch operation
git: high efficiency because the three-way merger
Branches can be divided into two types: long branch, short-term branch
Long-term branches: long-standing branches.
Short-lived branches: the destruction of the exhausted branch (question centralization)
PU branches: branch poor stability
Add a remote repository: git remote add <remote database alias> <URL remote repository>
View all repository branch: git branch -a
Update the remote repository: git fetch
Updates all remote repository: git fetch origin
The update remote database synchronization to the local branch of Operation: git pull <remote database name> <branch name>
pull <= equivalent => fetch + merge
Check local branch and a remote branch of the association: git branch -vv
Current branch synchronous remote branch origin / remote_branch: git checkout -t origin / remote_branch
to sum up:
In collaborative development, you can create some long-standing branch in the project maintains a fixed stage or the final result code and maintain code at different levels of stability
Short-term use of branch management development tasks allows developers to focus more on work
Use push and pull commands in real-time two-way local and remote synchronization code library.
Under what circumstances, give your local library to create multiple remote database?
In very fast iterative version of the case
