Ah, I love coherent software.

Not gonna lie, the master branch thing has been perceived as problematic but I don't typically see an issue with it. It's similar to master bedroom or bath. ~~Kind of fucked up name origin, but~~ I don't think anyone's really making a fuss about it.

Whatever the fuck you're doing though feels like some gross, racist fantasy. It's really weird, dude. If you think that's funny you might need to go talk to some real people or touch grass.

You could do that, but I could argue that master/slave nomenclature isnt a good scheme for this anyway, since it doesn't control any other branches. Unlike master and slave drives from the olden days.

By all means go ahead and keep your naming schemes. It's your own stuff that after all, that for some reason you felt the need to tell everyone about. However, I might recommend trying to move past it seeing as language has an impact on how people think, and being edgy doesn't exactly have a good track record of producing the best people.

Yeah, current company has their internal git server default to master and it was a little odd first time I created a new repo. Luckily all the CI templates can recognize either name so I just switched it.

git checkout -b main
git branch -D master
git config --global init.defaultBranch main

You don't have to deal with shit if you don't want to.

If you haven’t already found it, you need to change your global git config (~/.gitconfig):

git config --global init.defaultBranch main

(or whatever you want to call it; e.g. daddy would work too)

For any existing repositories you want to run the following command in the existing repository root (./.git/config):

git config set init.defaultBranch main