• It tries its best to default to master.
  • it always creates a master branch.
  • it throws a bunch of errors when trying to push to main.
  • I always have to do some random fiddling to make it work with the main branch, but at least once I made master the main one instead.
  • it ruined a few releases of mine, by publishing the older branch.
  • apparently this is very abnormal, and no one saw things like this.
  • every time I initialize a new repo, I make sure to run a git clone to initialize it on my PC, which is called main, then it defaults to master for no known reason.
  • checked the .gitconfig file, and nothing unusual.
you are viewing a single comment's thread
view the rest of the comments
[–] 3 points 10 months ago

I don't know the incantation offhand, but certainly there is a way to tell your git to treat 'main' as the default.

However, 'master' actually was the historical default; 'main' is a newer name (search online if you are interested in why some repos and git hosting providers switched to use 'main' ... warning, opinions differ on whether said reasons were considered sensible or not).

  • source