Hello, this depends on many things, like you agreed workflow (even if you work alone, you should agree with yourself). There are [1] and [2] as notable examples.
Basically, I would say yes, you should switch to master (git checkout master) and merge your changes (git merge your-other-branch). Best, Gergely [1] http://nvie.com/posts/a-successful-git-branching-model/ [2] http://scottchacon.com/2011/08/31/github-flow.html On 21 September 2014 12:11, Kunal Bajpai <kunal.baj...@gmail.com> wrote: > I have been using Git for about 2-3 months and have been using it on command > line for about a week. I wanted a little help with best practices using Git > & branching. > > I had created a branch out master committed some code to the branch & pushed > it to the remote with same name. But now how do I push the latest code on > the current branch to the master. > > Should I merge the current branch to master? What is the best thing to do in > this scenario? > > -- > You received this message because you are subscribed to the Google Groups > "Git for human beings" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to git-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
