Dear all,
circling back to the roots of this initiative, does anyone have a
reasonably high-level contact at GitHub?
While GitHub provided the near minimum in tooling around renaming away
from 'master', there's still considerable toil and friction involved;
in particular because it's one big change, not a series of small ones.
I would like GitHub to create a symlink of sorts when renaming:
'master' should autotrack 'main'. That would allow tooling,
integrations, and fetch/update to continue working with both branches,
allowing some time for coordination and moving. During this transition
period, all access to 'master' should be logged and presented to
admins/owners of the respective org/repo. This would allow tracking
down old usage and safely deleting 'master' once a large enough
fraction of users and tools have migrated. Pushes or merges to
'master' would be rejected with a server-side message telling the user
how to change local tracking branches.
Ideally, this would be a setting on both org and repo level.
If I may dream, local Git could even pick these server messages up and
switch over automatically, though that has security implications and
would need an allowlist in gitconfig.
Grafana has hundreds of repos, Prometheus dozens, several other
projects I am involved in also have two figures of repos each.
Co-ordinating all of those migrations is a near insurmountable
toilfest with a seemingly simple automated solution.
This ask has been sitting on Twitter[1] and as ticket 1119523[2] with
GitHub since April 23rd without any movement at all.
Any and all help appreciated,
best,
Richard
[1]
https://twitter.com/TwitchiH/status/1385597550237978626
[2]
https://support.github.com/ticket/personal/0/1119523