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!

    • killingspark@feddit.orgEnglish
      21·
      3 days ago

      The only thing I’m missing in the CLI is easy picking and choosing which change to include in a commit on a more fine grained basis than files. I sometimes have a changed file and the changes fix different issues and thus should get separate commits but with the CLI I can’t easily select the changes to be staged. At least not AFAIK.

      Edit: Richards law of posting something wrong to get fast correct answers seems to stay true, even on lemmy. Thanks for teaching me something today <3

      • The2b@lemmy.vgEnglish
        6·
        3 days ago

        You can via git add -i foo.bar

        I believe the only issue with that is that it can only go by hunks. If your changes are sufficiently far away, you can select them separately. But if you change one function that should be in patch a, and another function 5 lines down that should be in patch b, I think you’re screwed

        That being said, this is all from memory, so don’t quote me on it

        • Corngood@lemmy.ml
          8·
          3 days ago

          In interactive add mode you can use s to split a hunk, and e to edit it. That’s usually enough for me to split things up.

        • hallettj@leminal.spaceEnglish
          6·
          3 days ago

          I usually use git add -p to selectively stage hunks. But in git add -i I think running the patch command does the same thing to get into patch mode.

          If patch mode shows you a hunk, and you only want some of the lines you can press s to split into smaller hunks. Then you’ll be prompted whether to add each smaller hunk separately.

          If you want to stage a change that is on the same line as a change you don’t want to stage, or on an adjacent line, then you need to use e to edit the hunk. Git stages whatever changes are left when you’re done editing. The file in the working tree on disk is unchanged.

    • AdamBomb@lemmy.sdf.orgEnglish
      8·
      3 days ago

      Same, because its UX is actually really good. Years ago when I was new to git, I tried to use Sourcetree to revert a merge commit, and it would just fail. When I tried it in the CLI, it still failed, but it told me how to fix it. (I needed to specify which parent)

      That, plus it’s scriptable, plus I’m in the terminal a lot anyway. I’ll also use the IDE git client sometimes if that’s where I am at the moment.

    • pinball_wizard@lemmy.zip
      6·
      2 days ago

      CLI first here too, for the same reason.

      I’m not above using an editor plugin if it’s simple and reliable and right there waiting, like VSCodium.