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 bamboo@lemmy.blahaj.zone !

  • @FooBarrington@lemmy.worldEnglish
    3•2 months 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.

      • @FooBarrington@lemmy.worldEnglish
        0•2 months 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.

        • clifEnglish
          2•2 months ago

          I’ll find something else to screw up and cause it to break, don’t worry.