Yeah, ive had issues with repos on github having master and new ones having main. Github api seems to force the default branch to main (on new repos) making fixing this harder as well.
It's not that big of a deal but sure is a hassle.
It's not that big of a deal but sure is a hassle.
They're sure suggesting it - their suggested commands to initialize a new repo will create a main branch. But you can just ignore that suggestion?
They are just going along the git default, so yes, a new repo will be on main branch by default.
Here’s the API reference: https://docs.github.com/en/rest/reference/repos#create-an-or...
I don’t see any parameter for setting the default to master instead of main. However it does seem like you can change it after it has been created with a subsequent update call.
But that's why I'm asking where OP found that and not just saying they're wrong.
€: There's also https://docs.github.com/en/rest/reference/repos#update-a-rep... where you can set the default_branch?
Jesus, really? I didn't pay much attention to the master nonsense because I figured it would be limited to projects who cared more about social performance than building something useful, but it sounds like it's being forced at the platform-level onto every project.
OTOH, the impact is mitigated for new projects