• _MusicJunkie@beehaw.org
      link
      fedilink
      arrow-up
      2
      arrow-down
      4
      ·
      4 months ago

      For each project there is one authoritative instance, one “server” that everyone pushes to. Otherwise you get chaos.

      • Asyx@lemmy.ml
        link
        fedilink
        arrow-up
        9
        ·
        4 months ago

        That’s not a git thing though. You can totally have multiple remotes and the remotes are just git repositories themselves. Git is 100% decentralized. There is technically nothing stopping you from having multiple remotes.

      • perishthethought@lemm.ee
        link
        fedilink
        English
        arrow-up
        6
        arrow-down
        1
        ·
        edit-2
        4 months ago

        That may be how you use it, but that’s not baked into git. See my previous response. There’s a bunch of FUD in this thread for some reason.

        • Thann@lemmy.ml
          link
          fedilink
          English
          arrow-up
          2
          ·
          4 months ago

          People want simple answers, and “blockchain bad” seems to satisfy many

      • Thann@lemmy.ml
        link
        fedilink
        English
        arrow-up
        3
        ·
        4 months ago

        And nobody ever forked a project, and lived happily ever after, then end.

        • _MusicJunkie@beehaw.org
          link
          fedilink
          arrow-up
          1
          arrow-down
          1
          ·
          4 months ago

          If you want to work with the original project, you have to push to the server that controls the original project.

          • Thann@lemmy.ml
            link
            fedilink
            English
            arrow-up
            3
            ·
            4 months ago

            No you don’t, you can just fork it, add a commit, and walk away, and everyone can decide which one they want to clone