• dan@upvote.au
    link
    fedilink
    arrow-up
    8
    arrow-down
    5
    ·
    edit-2
    1 year ago

    Honestly, just use a GUI. Graphical user interfaces were designed for a reason. I usually use SourceTree or the Git functionality built in to Visual Studio or VS Code.

    It’s good to know how things work under-the-hood (e.g understand Git’s object model, some basic commands, etc) but don’t feel like you need to use the command-line for everything.

    • zalgotext@sh.itjust.works
      link
      fedilink
      arrow-up
      13
      ·
      1 year ago

      In my experience, using GUIs is how people fuck themselves, and then I have to unfuck them via the command line.

      Git’s interface is bad, yes. It has a step learning curve, yes. But I truly think the only real way to overcome those obstacles is to learn how git works, learn all the nitty gritty details, not hide from them.

      • CapeWearingAeroplane@sopuli.xyz
        link
        fedilink
        arrow-up
        4
        ·
        1 year ago

        I use a GUI (GitKraken) to easily visualise the different branches I’m working on, the state of my local vs. the remote etc. I sometimes use the gui to resolve merge conflicts. 99 % of my gut usage is command line based.

        GUI’s definitely have a space, but that space is specifically doing the thing the command line is bad at: Visualising stuff.

    • lseif@sopuli.xyz
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      lazygit or tig are terminal interfaces for git. very nice, best of both worlds imo. every action shows the git command ran at the bottom, and its a lot easier to see at a glance the status, diff, log, etc.