So creating a new repo on GitHub, you get a set of getting started steps. They changed the default branchname to “main” from “master” due to its connotations with slavery.

When I create a new repo now, the initial getting started steps recommend creating a branch named “master” as opposed to “main” as it was a while ago.

It’s especially weird since the line git branch -M master is completely unnecessary, since git init still sets you up with a “master” branch.

Disclaimer: I have a bunch of private repos, and my default branchnames are pretty much all “master”.

Is this a recent change?

Edit: Mystery solved, my default branchname is “master”. Thanks [email protected] !

  • @FooBarrington
    link
    English
    08 hours ago

    And yet not everyone used to use master, so scripts kept breaking for no good reason.

    Either make it a standard, or stop assuming it’s a standard. De-facto isn’t good enough.

    • @[email protected]
      link
      fedilink
      English
      28 hours ago

      Having a magical standard fairy waive a wand isn’t going to fix scripts, or stop them from breaking.

      • @FooBarrington
        link
        English
        17 hours ago

        What? If there’s an actual standard, it will stop scripts from breaking, because the assumption that master is the main branch will always be true.