It is NOT inclusive. :red_angry_face /s
I wonder what it could go wrong. This will be super funny when we'll see Golang libraries switching to the main branch instead. Lots of CI pipelines breaking because of that I guess
A little overly-dramatic for this particular instance, but this and the following results should be a very good signifier at just __how much__ power GitHub (i.e. Microsoft) has over the entire OSS/Non-OSS/Developer community (how many package/plugin-managers and other pieces of software pull from GitHub first/by default?), and how wantonly they will wield it. This change is going to most likely break a non-zero amount of workflows (and could you blame people for expecting what has been the standard convention since the dawn of time (exaggeration) to stay the same?), and for what? Something with no technical reason whatsoever!
it would be interesting if in Git, a branch "alias" or "redirect" were able to be created to prevent (or at least reduce) the possibility of experiencing broken links
Btw, how about the blacklist and whitelist? Are we going to replace those terminologies too?
Still a shame that this we now have two competing conventions what I consider to be no discernable reason.