Rename default branch from master to main about opentesarena HOT 6 CLOSED

I'd feel more confident about it after I merge my text-rendering-redesign branch, which could be a couple weeks still (don't know for sure). But I like the idea.

Git is a weird name to begin with ("an unpleasant or contemptible person" based on Google), so any improvements in the names of things associated with it are reasonable I think.

from opentesarena.

Should be all done. I verified in GitHub Desktop and my Windows Subsystem for Linux, and am about to on my Raspberry Pi.

On GitHub Desktop, I clicked Fetch then switched from master to main, it did some automatic things while switching, and then I switched to master and deleted it.

from opentesarena.

Yeah we should do it as long as it doesn't break or otherwise mangle any of the Git history.

from opentesarena.

It shouldn't break or mangle any of the Git history. I've done this with a few projects using Bitbucket Enterprise, although not on GitHub itself

Since Git branches are technically just pointers to commits, all we're doing is creating a separate branch pointed to the same commit, and then telling GitHub that's the default one.

from opentesarena.

Git is a weird name to begin with ("an unpleasant or contemptible person" based on Google)

According to Wikipedia, it was intentional:

Torvalds sarcastically quipped about the name git (which means "unpleasant person" in British English slang): "I'm an egotistical bastard, and I name all my projects after myself. First 'Linux', now 'git'."

from opentesarena.

I've renamed a few projects in GitHub and only issue is CI and any script that uses branch names.
About PRs there's no issue, in fact GitHub will notify users with open PRs and take care of repointing them.

from opentesarena.