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.

Off topic: day-after-day with these kinds of posts and especially the replies, I need Reddit less and less. That’s a very good thing.

The cli because it is consistent everywhere and has all fearures

Lazygit.

vscode with edamagit and the cli

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.

Lazygit and magit

LazyGit and GitKraken. I try to use LazyGit as much as possible, but a few things are easier for me in GitKraken (as I’m more used to it).

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.

Lazy git most of the time, sourcegit for heavy duty stuff.

Github desktop, despite the name it’s just a git client. Absolutely clownish that there’s no official Linux support (there’s a fork which works perfectly). I use it to interact with self-hosted gitea, codeberg and github, pretty happy with it, I’m Aldo testing git butler

CLI with some aliases for viewing commit history and branching, or less frequently an IDE plugin

Is Vscode a git client?

No one take from me though idk what I’m doing when it comes to programming stuff.

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

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.