git_branching
| Hometown: | Melbourne, Australia |
| Specializations: | Java, Ruby on Rails |
| University: | Software Engineering & Economics, Melbourne University |
| High School: | VCE, Melbourne High School |
| Links: |
|
We've recently needed to manage some remote branches in GIT (create and delete them). Having stumbled around google for ages trying to figure out how to do this seemingly simple task, we came up with this list of 5 commands:
- git push origin listing_edit_steps_spike:refs/heads/listing_edit_steps_spike
- git fetch origin
- git config branch.listing_edit_steps_spike.remote origin
- git config branch.listing_edit_steps_spike.merge
- git checkout listing_edit_steps_spike
These are the commands that the git_remote_branch tool (http://grb.rubyforge.org/) uses when you use it to create a remote branch. Whats with all the config updates? Whats with the origin fetching? And what is with all of those damn confusing arguments?
Honestly, as a developer, I couldn't care less. I just want to be able to manage remote branches quickly and easily and not have to freken google for 15 minutes everytime I need to get the job done!
Apparently GIT is supposed to be our saviour. If thats the case, then I'd rather go on living in "hell"...
Sound Convoluted and overly complicated?!
Yes ... it is ... Especially when compared to this:
svn copy [SRC] [DEST]
But apparently SVN is crap, right?
Comments ...
create new branch:
git checkout -b my_new_branch
push branch to origin:
git push origin my_new_branch
simple as that.
all the config stuff you had going there, im not even sure what it means. i suppose its a more convoluted way to things, or the environment is not set up correctly.
sure an svn copy seems easier, what you are missing is an example of the source and destination, which looks something like this (from google hehe):
svn copy http://svn.example.com/path/to/repository/trunk http://svn.example.com/path/to/repository/tags/snapshot-of-trunk
i dont see that as simple. plus there is the other end of creating branches which youve neglected. merging! git is kinder to use when merging needs to happen