I’m wondering if you use any (graphical) clients to manage your Git, and if so, what client you use.

I myself have to use git professionally across all 3 major OS-es, and I currently use Sourcetree on Windows and macOS, and the Git tools built-in into IntelliJ on Linux.

Have given MaGit a try, but just couldn’t get all the shortcuts to stick in my mind.

Interested to hear your experiences!

  • KissakiEnglish
    8·
    2 days ago

    TortoiseGit.

    Through settings, I move the Show Log to the top context menu level, and it’s my entry point to every Git operation.

    I see a history tree to see and immediately understand commit and branch relationships and states. I can commit, show changes, diff, rebase interactive or not, push, fetch, switch, create branches and tags, squash and split commits, commit chunk-wise through “restet after commit”, … And everything from a repo overview.

    /edit: To add; other clients I tried never reached what I want from a UI/GUI, never reached TortoiseGit. Including IDE integrations where I’m already in the IDE; I prefer the separate better TortoiseGit.

    GitButler is interesting for it’s different approach, but when I tried it out the git auth didn’t remember my key password. (Since trying out jj I found out it may have been due to disabled OpenSSH Service.)

    • Creat@discuss.tchncs.de
      1·
      2 days ago

      I have a love-hate relationship with it. Due to work reasons I’m more familiar than I want to be with tortoiseSVN, and the git version is similar enough to feel at home. But that’s also it’s biggest downfall: it does a lot of things the “SVN way” despite being a git client. The workflow can be kinda made to work, but it always feels like it’s not a native git tool, because it isn’t. I would go so far as to say that it encouragedrl bad habits on git, especially for those used to tortoiseSVN.

      • KissakiEnglish
        1·
        14 hours ago

        What do you mean in particular?

        The only thing that comes to mind for me is the “restore after commit” being a different chunk-add workflow than add --patch - but I don’t think it’s worse.