On 11/06/2020 13:52, Derrick Stolee wrote: > On 6/11/2020 7:59 AM, Don Goodman-Wilson wrote: >> On Thu, Jun 11, 2020 at 1:52 PM Michal Suchánek <msuchanek@xxxxxxx> wrote: >>> Indeed, the flexibility to choose the name of the default branch can be >>> helpful for projects with specific naming, especially non-english >>> speaking projects. >>> >>> To that end I would suggest adding -b argument to git init to be able to >>> choose the default branch name per project. This should select the >>> initial branch name and also write the it as the default branch name in >>> the repo configuration (if git continues to treat the default branch >>> specially). >>> >>> This can be used in documentation to use the new name immediately >>> without breaking existing workflows that rely on the 'master' branch. >> I _really_ like this idea (and your reasoning). Seconded. > Yes, adding a -b|--branch option would be an excellent addition to > the config option. > > Is their also an option to also add an option to `git clone` to (re)set the default branch name offered by the upstream to that provided? Alternatively provide a `--no-checkout` option for the clone so that either no actual checkout is performed, or maybe that a detached head checkout is performed so that users can name their default branch appropriately. In some cases a true --no-checkout may be the 'best' thing to do to avoid the user mental model confusion about needing to have a local branch matching an upstream branch before they can start their work on top of it (hopefully with a fresh branch name). Philip
