You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This came up a couple of times, and I personally am so used now to "main" being the default branch, that I constantly get confused.
The move itself is effortless, and GitHub provides some guidance as to how to change it locally if the move is done (I have done this a few times).
Please let us know, if you know of a reason not to do this rename, or to postpone it.
The text was updated successfully, but these errors were encountered:
The only reason for me (but it is not a huge problem, frankly): some scripts (Dependabot, my own, Yocto/OE, maybe some distros) fetch sources by branch name.
Thus, as a general rule: if there are no other reasons to change something, please, do not do it just for fun.
Well, there is no really compelling reason for this, other than the reasoning behind the original renaming, and the fact that this is now the git standard for several years and many repos have been switching. I have done the switch for a few repos myself, so far without any problems. And yes, I often get confused calling mastermain, because I'm now so used to it...
Admittedly, this is not consistent inside the MeVisLab organization either - the two other actively maintained repos use main, while the (currently) inactive ones still use master.
This came up a couple of times, and I personally am so used now to "main" being the default branch, that I constantly get confused.
The move itself is effortless, and GitHub provides some guidance as to how to change it locally if the move is done (I have done this a few times).
Please let us know, if you know of a reason not to do this rename, or to postpone it.
The text was updated successfully, but these errors were encountered: