Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have a simple question about git.
I would like to know what is the common way to use branch.
Figure out you create a branch for authentication that you don’t finish or where you will add other stuff later. Then you work on another branch, for example relationship.
If now, I finish what I have to do on relationship and I want to add my stuff about authentication. Did I have to switch to the authentication branch or do I have to create another one?
Thanks
Branches are for anything that is independent. Want to work on a new feature? Make a branch. Want to work on fixing a bug that will probably take more than a few minutes to fix? Make a branch. Want to toy around with different configurations? Make a branch.
Branches in Git are very lightweight, so never be afraid to branch out and do something. When you want to bring changes back together, you simply use the
git mergecommand to merge changes from one branch back into another.