• ShustOne@lemmy.one
    link
    fedilink
    arrow-up
    5
    ·
    9 months ago

    I use GitHub and all my older repos have a master branch with no forced change. When did they force a change? I think you are mistaken.

    • MeanEYE@lemmy.world
      link
      fedilink
      arrow-up
      4
      arrow-down
      1
      ·
      9 months ago

      Had to refresh my memory, it’s been a while. They didn’t change branch on existing projects, but they did change it on new repos to main by default. Our tools indeed created repositories and configured everything for the developer automatically. However GitHub’s policy meant that you had to either change the tools to detect whether they are working with old repo or new, or go to every new project after automatic configuration fails, configure default branch and then rerun the tool. Same thing then happened to few of our tools that were used for CI.

      All in all they made more work for us for no reason other than be smug about it and it changed exactly nothing.

      • EarMaster@lemmy.world
        link
        fedilink
        arrow-up
        2
        ·
        9 months ago

        So your tooling was at fault for assuming something that has always been declared a convention not a rule. It is like assuming we will never reach the year 2000 and there only storing the last to digits for the year…

      • ShustOne@lemmy.one
        link
        fedilink
        arrow-up
        1
        ·
        9 months ago

        I think this is an excuse. Using the CLI you can easily create and specify the default branch. It’s also not difficult to check the branch name.