Right now, the master branch is kind of useless, and not really recommended to be used.
But, master is the default checked out branch after clone, so this might confuse lots of people.

To solve this, we just need to add a git setting for each project to specify the "Default branch"
See IRC Conversation below:

sdboyer: So the question lots of people are asking is "how to handle the master?"
langworthy: the branch you get when cloning without the --branch parameter is determined by a serverside repo setting that we can control, but we have not made a UI available for controlling it yet
arlinsandbulte: easiest answer is "don't use it"
sdboyer: hmm. That sounds interesting. (serverside repo setting for default branch)...
yep. it's not a complicated setting, not at all. creating a job to write to it would be trivial. the question is where to put it in the UI
sdboyer: is there an issue or discussion about that somewhere?
sdboyer: i think vc_project could expose a repo settings tag or something like that, and vc_git could alter the setting in there
arlinsandbulte: there might be an issue, i don't know
mikey_p: sure, that sounds quite feasible. it's more that it's one of a deluge of settings/controls related to the repo that we need to find a place for, and there's no clear place to slot it in
a repo tab has been brought up before, and i'd be fine with that
just...needs a decision is all :)
* mikey_p will role a patch for vc_project sometime before the end of Drupalcon ;)
sdboyer: ah. like the 'Default Branch' option in GitHub.

Comments

arlinsandbulte’s picture

Ah crap, the IRC conversation was borked by the filter.
Read this instead:

--arlinsandbulte-- sdboyer: So the question lots of people are asking is "how to handle the master?"
--sdboyer-- langworthy: the branch you get when cloning without the --branch parameter is determined by a serverside repo setting that we can control, but we have not made a UI available for controlling it yet
--sdboyer-- arlinsandbulte: easiest answer is "don't use it"
--arlinsandbulte-- sdboyer: hmm. That sounds interesting. (serverside repo setting for default branch)...
--sdboyer-- yep. it's not a complicated setting, not at all. creating a job to write to it would be trivial. the question is where to put it in the UI
--arlinsandbulte-- sdboyer: is there an issue or discussion about that somewhere?
--mikey_p-- sdboyer: i think vc_project could expose a repo settings tag or something like that, and vc_git could alter the setting in there
--sdboyer-- arlinsandbulte: there might be an issue, i don't know
--sdboyer-- mikey_p: sure, that sounds quite feasible. it's more that it's one of a deluge of settings/controls related to the repo that we need to find a place for, and there's no clear place to slot it in
--sdboyer-- a repo tab has been brought up before, and i'd be fine with that
--sdboyer-- just...needs a decision is all :)
* mikey_p will role a patch for vc_project sometime before the end of Drupalcon ;)
--langworthy-- sdboyer: ah. like the 'Default Branch' option in GitHub.

arlinsandbulte’s picture

Project: The Great Git Migration » Version Control / Project* integration
Version: » 6.x-2.x-dev
Component: Workflows » User interface
Josh The Geek’s picture

Status: Active » Closed (duplicate)

You might want to repost, this is a duplicate of #1074960: Let maintainers set a default branch on git repositories.

arlinsandbulte’s picture

Thanks for the redirect, Josh.

arlinsandbulte’s picture

Thanks for the redirect, Josh.