The actual operation of Git branch development

This article introduces the relevant knowledge of "the actual operation of Git branch development". In the operation of actual cases, many people will encounter such a dilemma, so let the editor lead you to learn how to deal with these situations. I hope you can read it carefully and be able to achieve something!

1. Everyone develops the operation flow in this way on a branch, which is not much different from svn. It is simple and rough local operation: first git add and then git commit remote synchronous operation: first git pull and then git push. If it is a collaborative development by multiple people, you will find that every time you push after pull, there will be one more merge record. If you don't think it looks good, you can follow the following process: first git pull, then git rebase the last git push2, pull a new branch for each requirement, for example, the oa project has a new requirement, 101git checkout-b feature-oa-101 development, complete, after local commit, do not push to remote Then merge: git checkout devgit merge-- no-ff-m "merge feature-oa-101 to dev with no-ff" feature-oa-101git push and then delete branches: git branch-d feature-oa-101 if not merged, make sure that this requirement is definitely not wanted, do not merge, directly delete: git branch-D feature-oa-101 "actual operation of Git branch development" content is introduced here, thank you for reading. If you want to know more about the industry, you can follow the website, the editor will output more high-quality practical articles for you!