Git--Introduction to branch management

Branching is the parallel universe in sci-fi movies, and while you're working on git in front of your computer, another one is working on SVN in another parallel universe.

If two parallel universes don't interfere with each other, that's not going to affect you now. However, at some point in time, two parallel universes merged, and as a result, you learned both Git and svn!.

What is the use of branching in practice? Suppose you are ready to develop a new feature, but it takes two weeks to complete, the first week you write 50% of the code, if submitted immediately, because the code is not finished, the incomplete code base will cause others can not work. There is a huge risk of losing your daily progress if you wait until the code is all written and then submitted again.

Now that you have a branch, don't be afraid. You create a branch of your own, others do not see, but also continue to work on the original branch, and you work on your own branch, you want to submit the submission, until the development is complete, then once merged into the original branch, so that it is safe, and does not affect the work of others.

Other version control systems such as SVN have branch management, but after use you will find that these version control system creation and switching branches than the snail is still slow, it is unbearable, the results branch function became a device, we do not use.

But git's branches are different, and git can do it in 1 seconds, whether it's creating, switching, or deleting branches! Whether your repository is 1 files or 10,000 files.

Git--Introduction to branch management