Matteo Lissandrini (AAU)
I think I can reassure you on practical issues:
1) so Github is already working on this: https://twitter.com/natfriedman/status/1271253144442253312?ref_src=twsrc%5Etfw
2) the rename is maybe an issue for existing local branches/forks/clones with active changes, which I would guess are at best a handful.
3) when we create a new repo on github, creating the appropriate branch and delete master is probably a matter of five minutes?
Instructions to change the default branch exist already:
a) On github: https://help.github.com/en/github/administering-a-repository/setting-the-default-branch
b) On local&github: https://www.hanselman.com/blog/EasilyRenameYourGitDefaultBranchFromMasterToMain.aspx
c) automatically on new repos: https://superuser.com/a/1559582/762700
Department of Computer Science
From: email@example.com <firstname.lastname@example.org> on behalf of tomas Navarrete via groups.io <email@example.com>
Sent: 17 June 2020 17:07:20
Subject: Re: [bonsai] Change branch name in GitHub #communication #project
I totally understand the reason behind the wish to change names.
Now, beware that:
The default branch name in Git is master.git-scm.com/book<https://git-scm.com/book/en/v2/Git-Branching-Branches-in-a-Nutshell#ch03-git-branching>
so, every time we create a new repo, or initialize one, we'll need to update this behavior (MAYBE until github does something about it ... which is funny, because they kind of have a dominating position in the "free git hosting" namespace ;) )
For very practical reasons, I would stand against renaming existing repositories and only apply a name change on newly created ones, and loudly anounce this in the README of the repo.
If this (default branch name) is configurable, then we should look to implement a name that is fine with us.