• lightnegative@lemmy.world
        link
        fedilink
        arrow-up
        12
        ·
        8 months ago

        Do it enough times and it stops being scary.

        Using a tool like VSCode to perform the actual merges on individual files also helps because it shows what “yours” and “theirs” changes are from a user perspective, not a git perspective

        • boomzilla@programming.dev
          link
          fedilink
          arrow-up
          2
          ·
          8 months ago

          The 3-way merge editor in VSCode is a fantastic tool. Really helps in visualizing what comes from where and preventing merge accidents.

      • buzziebee@lemmy.world
        link
        fedilink
        arrow-up
        2
        ·
        8 months ago

        It’s doable once you know what you’re doing. I can do it all via the cli, but I personally use gitkraken most of the time and it’s just so much easier and more ergonomic.

        I also see a lot of the Devs who insist they know what they’re doing create horrible messes of their branches super easily via the commit tree. People should just use whatever works best for them to get the job done.

    • oce 🐆@jlai.lu
      link
      fedilink
      arrow-up
      13
      arrow-down
      1
      ·
      edit-2
      8 months ago

      If it was dead simple you wouldn’t need to learn 10 new concepts and google commands regularly even after using it for a couple of years. You probably forgot how you struggled at first. I have taught it multiple times and I see how beginners struggle.

    • sajran@lemmy.ml
      link
      fedilink
      English
      arrow-up
      4
      ·
      8 months ago

      I would actually say it’s VERY complicated but in daily work you probably need like 5 commands and those aren’t hard at all.