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!

  • tiredofsametab@fedia.io
    link
    fedilink
    arrow-up
    1
    ·
    2 days ago

    I have tortoise git on a windows machine and GitHub desktop on a Mac. I do some things from the command line when I’m not feeling lazy.

    • SinTan1729@programming.dev
      link
      fedilink
      English
      arrow-up
      2
      ·
      edit-2
      5 days ago

      I mostly use git from the cli, but when I want to use a frontend, I use lazygit. (I just find it easier to use TUI for some things like only committing some of the changed files, squashing, or fixup commits.)

  • koala@programming.dev
    link
    fedilink
    arrow-up
    1
    ·
    3 days ago

    When I learned Git I think there were not decent tools, so I got used to the command line.

    I occasionally use gitk for reviewing my commits- it’s nicer to see the files modified and be able to jump back and forth, although I get I could use git log -p instead.

    I’m an Emacs user, but I don’t use magit (!)

    I like some of the graphical tools- some colleagues use Fork and I like it… but as I’ve already learned the CLI, I don’t see the point for me.

    I could use learning some jj because it automates some of the most tedious parts of my workflow, but I’m getting too old.

  • bignose@programming.dev
    link
    fedilink
    English
    arrow-up
    7
    ·
    5 days ago

    Magit is what allowed me to finally commit to switching to Git full time.

    It’s such an excellent front-end for Git that I’ve known numerous workmates learn Emacs just to use Magit.

  • Kissaki@programming.dev
    link
    fedilink
    English
    arrow-up
    7
    ·
    edit-2
    5 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.)

  • spartanatreyu@programming.dev
    link
    fedilink
    arrow-up
    5
    ·
    edit-2
    5 days ago

    Fork !!!

    It’s hands down the best git client.

    It’s free as in: sublime text or winzip where they ask you once a month if you want to pay for it but you can just select: I’m still trying it out, and it gets out of your way.

    • It’s got a well designed tree graph like in GitKraken except it doesn’t lag
    • It’s interactive rebasing is as smooth as JJ / LazyGit, so you can edit/rename/reorder your commits except you don’t have to have to remember CLI flags since it has its own UI
    • It’s lets you commit individual lines by selecting them instead of adding/removing whole hunks like Sourcetree except it isn’t filled with paper cuts where a feature breaks in an annoying way for 2 years and you have to do extra steps to keep using it how you want.

    And one killer feature that I haven’t seen any other git clients handle: allowing me to stage only one side of the diff. As in: if I change a line (so it shows up as one removed line and one new line in git), I can decide to add the new line change while still keeping the old line.

    So changing this:

    doThing(1);
    

    into this:

    doThing(2);
    

    Shows up in git as:

    - doThing(1);
    + doThing(2);
    

    But if I still want to keep doThing(1);, I don’t have to go back into my code to retype doThing(1);, or do any manual copy-pasting. I can just highlight and add only doThing(2); to the staging area and discard the change to doThing(1);.

    So now the code exists as:

    doThing(1);
    doThing(2);
    

    Now with a one-liner example like this, we could always re-enter the code again. But for larger code changes? It’s far easier to just highlight the code in the diff and say: yes to this and no to the other stuff.

    And when you get used to it, it makes it really easy to split what would be large git commits into smaller related changes keeping your git history clean and easy to understand.

    • ILikeTraaaains@lemmy.world
      link
      fedilink
      arrow-up
      3
      ·
      4 days ago

      I love Fork, bought the license to support the developer.

      The only thing I don’t like is that there is no Linux version, asked the dev and he told me that the issue with Linux is that there are different distros with different GUI libraries so it would require multiple versions for Linux.

      A bit saddened it I completely understand.

      • spartanatreyu@programming.dev
        link
        fedilink
        arrow-up
        2
        ·
        2 days ago

        I paid for it too!

        It’s the first piece of shareware I actually went out of my way to pay for because it was so good that I’d be genuinely pissed off if it died. I’d probably end up switching to pijul or something else for my projects if it ever did.


        I’ve seen a bunch of people messing the windows version running in linux in the fork forums, so it may be coming in an unsupported capacity.

    • fox2263@lemmy.world
      link
      fedilink
      English
      arrow-up
      2
      ·
      4 days ago

      I’ll second Fork, it’s been my go to for years! Maybe I’ll pay for it one day

  • Zarlin@lemmy.dbzer0.com
    link
    fedilink
    arrow-up
    6
    ·
    edit-2
    5 days ago

    Fork on windows, SourceGit on Linux, both have a similar UI layout to SourceTree, but are much faster/snappier.

    I really like having a clear overview of the commit history, branches and current local state. I haven’t figured out yet how to get such an “at a glance” overview in the CLI.

    For advanced stuff the CLI is still very convenient.

    • Faalangst_26@feddit.nlOP
      link
      fedilink
      arrow-up
      2
      ·
      5 days ago

      Have to take a look at Fork (annoying name to Google I image). Sourcetree can be quite sluggish and downright annoying on macOS.

      Ditto on the CLI having its pro’s and cons

  • somegeek@programming.dev
    link
    fedilink
    arrow-up
    5
    ·
    5 days ago

    Lazygit. Used gitui for a long while but lazygit has vim key bindings which is much nicer and it also seems much more stable.