Most repos use the branch `master` as their default, but Git doesn’t force this upon you and why should we? Now you can change it to whatever you want. This means two things (using ant as an example):
- http://github.com/apache/ant redirects to http://github.com/apache/ant/tree/trunk
- git clone git://github.com/apache/ant.git will have `trunk` checked out by default
Oh, nice. I was looking for something like this yesterday.
/cheer
Will the automated gem builder continue to monitor the master branch or will it monitor the default branch instead?
oh! holy crap! I requested barely 1.5 days ago.
consider me a loyal subscriber forever.
This solves a problem I was going to have in about two weeks. Thanks, guys!
Ditto what mojodna said. Also, would love to have multiple gems for both the stable and master branches where the default one doesn't have any branch distiguishifier. E.g. chriseppstein-compass, chriseppstein-compass-master
Please please please make the branch dropdown more sane. We create branches every 2 weeks, and so our branch dropdown is pages and pages long, and if you don't have a mousewheel it's virtually impossible to find the branch you want. Please order them by creation date, newest first.
@lukec, you're doing it wrong. Use branches as active lines of development. Merge between branches when you hand code off or transition it to a new state of development. Add tags every couple weeks so that you can branch off of them if you need to.