Open ianheggie opened 1 year ago
There is the complication that since git is used as an installation mechanism, there are loads of people who are using the master
branch as an installation of rbenv-binstubs, not just developers contributing to the project.
As such, I wonder if it would be worthwhile to maintain the master branch for pulls and updates? (Presumably, github's branch rename feature doesn't actually support redirection for git:// urls or ssh? only http?)
The way I've done this in a few other projects is with a github action that simply fast-forwards master
every time main
is pushed. This way the default branch can be changed to main
, but existing installations (via git) don't break? Then at some point later, we can drop the syncing and delete the master branch altogether?
Although it doesn't affect me personally , I feel that renaming master to main is an appropriate signal of respect for the difficulties many people face.
https://github.com/github/renaming