Rename master branch to main #560
Conversation
This reverts commit 7da6a82.
|
I've reverted this PR. You do not merge a PR this disruptive without approval. We can make this change once v4 (next-gen) has been released. |
|
@BeyondEvil I would like to challenge you to explain what is disruptive about branch renaming? Over the last 2+ years, I did this on over a hundred of repos, and I am yet to see the what becomes disruptive. |
|
Every ref, fork and alias needs updating. |
|
Apparently you are not aware about the fact that github redirects old name to new one, so you can still clone and pull from outdated urls. They did it quite well. Even the PR are kept open. TBH; that is the first time when I see someone opposing that move. In fact before doing the rename I asked Ronny on irc about a possible wide move for the entire @pytest-dev so we could have consistent branch naming. Obviously that the wide move would need to be announced. |
|
Will GH fix my aliases too? This is my last response on this matter. You've sort of already proven my point about this being disruptive. It's also the most interaction I've gotten out of you for over a year. If pytest-dev decides to do a wide rename, they can do it. Until then, the rename won't happen until v4. |
|
ideally i want an eventual switch of all of pytest-dev to the "new" branch names, im fairly low on band-with for this myself for quite a while longer i believe for pytest-html the most painless switchover will when v4 lands |
No description provided.