My feeds this morning are entirely one story: GitHub saying it'll move away from "master" as the default branch name, with "main" the obvious replacement. The reactions split exactly where you'd expect, half declaring it overdue and half declaring it pointless, and very few people in either camp actually changing anything in their own repos today.
Here's the bit nobody wants to admit: technically this is trivial. It's git branch -m master main, a default in your config, and an update to whatever CI or deploy script has the old name hardcoded. The friction isn't the rename. It's the hundred places across an organisation where "master" is baked into a path, a webhook, a protected-branch rule or a half-remembered Jenkins job, and finding all of them is the actual work.
So I'll do the boring thing. New repos get init.defaultBranch = main locally, and I'll migrate the ones I own when I'm next in them anyway, not as a grand gesture but because consistency is worth more than the principle either way. The shouting will have moved on to something else by Friday. The config change will still be sitting there, quietly correct, long after everyone's forgotten which side they were loudly on.