Kind of wild how the primary branch of every git repo became "main" over the course of a year and how few things broke as a result.
@seldo I remember hearing people talking about how disruptive it was going to be

@hjharnis @seldo Yeah, that was great to see!

A key part of why it wasn't disruptive is that Git upstream, and the major Git hosts like GitHub and GitLab, did some thoughtful work to make a smooth transition away from "master" possible:
https://about.gitlab.com/blog/2021/03/10/new-git-default-branch-name/

The new Git default branch name

Why we're joining the Git community and updating "master" to "main".

@seldo it’s almost as if we can change our language to be more inclusive without Armageddon happening as a result!
@seldo sadly still trying to fight that battle on my team
@seldo Sigh. I jumped the gun a bit with some of @bffdotfm's repos and now we have a handful of `main` and handful of `trunk` and I've been putting off going in and changing it again to get aligned. But yes, turns out very few side effects.
@seldo only thing that broke was some tech dudes’ ego, which was a good thing
@seldo I have one customer who stuck with master, causing me repeated panics when I’m told main doesn’t exist, so count “my brain” in the what-broke column.
@seldo I remember the pearl-clutching panic about it too... and it just became normal & the sky didn't fall down.
@seldo Any (maintained) project that hasn't is, at this point, making a political choice. It's been long enough, and the sky didn't fall down.
@seldo I love that my team went “yep, sure, let’s do that right away” and we were all done with zero fuss.