renaming VS changesets

Uh, no. This is false. It’s just part of a broader trend to stop using ‘master’ due to some people finding that term offensive.

https://github.com/github/renaming

Not only did GH only make the change for reasons other than what you said, it's also just a weird hill to die on? Words evolve over time, and as things take on different connotations, people generally gravitate towards more tasteful alternatives.

I mean github changed "master" to "main" because social warriors were crying wolf on the use of "master"... people are going to find ways to get offended, once everything has been turned to "neutral" another side of the same group will fight for "inclusion" by turning all of it on its head.

The master-main thing is actually real lmao. Not Stanform, but GitHub did it

Oh, they did already. The default branch is "main" now if you create the project on Github. But if you're a white colonizer like me, you create your project using git directly and it uses master by default.

😱 the M-word

Github renamed the master branch to main. The University of Pennsylvania renamed faculty masters to faculty directors. There's a view to rename residential masters at Yale. Likewise, the master's degree should be renamed to something that's more racially sensitive.

At Frontside, we instead tie branches to major releases: everything that is merged into a v1 branch must be releasable in a v1.x.x version. That enables us to use changesets to cut minor and patch releases with minimal effort – even within monorepos.