• timbuck2themoon@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      21
      arrow-down
      2
      ·
      6 months ago

      Yes like companies who have thousands of repos with master as the main branch. It really wouldn’t make sense to switch halfway and be working on different repos with different primary branches.

      Not the biggest hurdle to overcome but also… Why should you have to?

      • fl42v@lemmy.ml
        link
        fedilink
        arrow-up
        6
        arrow-down
        1
        ·
        6 months ago

        Do you really have to, tho? One can keep using masters, move them to mains, or even symlink one to another so that everyone is comfortable with whatever they’re used to. Seems like a non-issue to me 🤷

        • wewbull@feddit.uk
          link
          fedilink
          English
          arrow-up
          3
          ·
          6 months ago

          We’ve ended up with a 50:50 chance of what any repo is doing. All depends on when the repo was created (old ones are all master) and if the creator tried to preserve consistency or not (yes: master, no: took the default of main).

          It’s annoying and pointless.

          • fl42v@lemmy.ml
            link
            fedilink
            arrow-up
            3
            ·
            6 months ago

            I mean smth like git symbolic-ref refs/heads/master refs/heads/main. Not sure if it’s a bad practice or smth, tho

        • MeanEYE@lemmy.world
          link
          fedilink
          arrow-up
          1
          ·
          6 months ago

          For a while, yes, you had to. Every new repo would be main while old ones remained master. Tools that default to a specific branch aside now you had to remember and check which branch you are merging into every time.

        • AggressivelyPassive@feddit.de
          link
          fedilink
          arrow-up
          1
          arrow-down
          2
          ·
          6 months ago

          It’s an issue, because many tools default to a certain branch, and people do too. So each build pipeline has to be changed, each dev has to check for each repo he’s working on, whether it’s using main or master, etc, etc.

          Just think about what hell would break loose, if Microsoft would be forced to rename C: to something else because someone was reminded of the "C word ".

    • Deebster@programming.dev
      link
      fedilink
      arrow-up
      12
      arrow-down
      2
      ·
      6 months ago

      On the plus side, forcing people to support alternative branch names surely has led to better software support for a core Git feature.

      • MeanEYE@lemmy.world
        link
        fedilink
        arrow-up
        3
        arrow-down
        2
        ·
        6 months ago

        That’s like forcing people to have different color shoe laces and calling it good practice. In reality it changed nothing but forced a lot of people to work on solving issues with their scripts and automation tools for the sake of change instead of spending that time on writing actual code and fixing bugs.

    • fl42v@lemmy.ml
      link
      fedilink
      arrow-up
      3
      arrow-down
      2
      ·
      6 months ago

      Sb got offended for no reason, then companies decided to get public approval points out of it; nothing new or notable. Seriously, tf is the point of overanalyzing it like there’s nothing better to do?

    • MeanEYE@lemmy.world
      link
      fedilink
      arrow-up
      3
      arrow-down
      3
      ·
      6 months ago

      This, sooo much this! People don’t realize that this change created a lot of unnecessary work to a lot of developers for no other reason than PR or to act smug about it. They solved slavery problem by renaming master to main equally well as they solved homophobia and transphobia by allowing people to specify pronouns on their profiles. Who the hell cares if you identify as tree sap. However many do care if your code sucks or doesn’t follow coding style.

    • lugal@lemmy.ml
      link
      fedilink
      arrow-up
      11
      arrow-down
      40
      ·
      edit-2
      6 months ago

      You sound like a slave owner, ngl

      I am not pro slavery but I will not free my chattel slaves. People just break with this tradition for extremely dubious reasons.

      Listen to yourself!

      Edit: I was thinking about putting “/s” at the end but thought it was obvious enough. I was wrong

        • lugal@lemmy.ml
          link
          fedilink
          arrow-up
          3
          arrow-down
          7
          ·
          6 months ago

          Why do I keep getting this comment? Maybe I should call myself Poe in the future

          • Deebster@programming.dev
            link
            fedilink
            arrow-up
            6
            ·
            6 months ago

            I think on the Fediverse (or just Lemmy?) I’ve seen more people who’d post your comment non-ironically. Or maybe they’re not serious either (but they’d have to be really committed to the bit).

            • lugal@lemmy.ml
              link
              fedilink
              arrow-up
              2
              ·
              6 months ago

              I had a conversation recently where someone said they weren’t serious after several levels of comments that were downvoted into oblivion. I try to make myself understood in the second (or third) level of comments or, as in this case, in an edit

            • lugal@lemmy.ml
              link
              fedilink
              arrow-up
              1
              ·
              6 months ago

              I guess I once again forgot the “/s”. I’m not going to call me “Poe” at any point of time /s