I ask because I like console, but at the same time have difficulties remembering all the commands. I’d like to try a GUI that is comfortable to use with only a keyboard.
[edit]
My inbox got fediversized, fantastic feeling.
It’s a paid app only available for Windows and Mac at the moment, but Fork may be worth a look: https://git-fork.com
I am using it too and I love it. I only know source tree as a competitor and in comparision it sucks…
You dont have to pay for it, even when using it comercially (unpess they changed that)
It has a “free evaluation” that I think can be as long as you want it to be / honor system.
Its been worth it to me to pick up a license and support the development though. Its reasonably priced (for a dev tool) / no subscription and definitely beats the free clients I was using before (Sourcetree/GithubDesktop).
Came here to recommend it too, really neat and practical tool and I haven’t found a better alternative yet. Honestly I don’t know why are people so against GUI git tools, it makes visualizing branches and commits so much more easier. I don’t think you can use it only with your keyboard as OP asked though, dunno how important that is to them.
Magit with emacs (doom emacs to be fully honest). More a TUI, but definitely fully keyboard driven :)
Yeah this is THE best interface for git. Worth getting into Emacs just to use it id say.
Magit on Spacemacs for me. Absolutely brilliant tool. https://magit.vc/
Same here. I don’t even use emacs for development anymore (I use IntelliJ since all my work is on the JVM and Typescript) but I still have an emacs running in the background for magit and org-mode. Magit is insanely effective for performing complex rebasing and cherry-picking tasks.
Lazygit changed how I use git, it is so easy to do all the daily essentials like branching, committing, and merging, but also also does more advanced things like interactive rebasing when needed.
I had searched for a proper git client, that was free and open source plus worked on both Linux and Windows, for a long time and I haven’t looked back after finding lazygit.
TortoiseGIT
It doesn’t get enough love.
These days I can run everything I need to with the git cli. I use the JetBrains visual merge tool to resolve conflicts, because doing that by hand is so awfully error prone, it very very intuitively maps to a visual process
Sublime Merge has been wonderful to work with
I also love how fast Sublime Merge is. The built in merge tool is great too. I’m a sucker for apps with a command palette for easy access to every command.
Definitely can recommend Sublime Merge as well!
It is one of the few tools that doesn’t misrepresent the core git paradigm.
I used to use SourceTree but it runs horribly and switched to Fork years ago and never looked back. I use VSCode for merge conflict resolution.
Same here, but I still like the merge conflict interface Fork has.
I’m still using SourceTree, I’ve tried a few others but have always gone back. Never heard of Fork tough, guess I’ll try that out.
I use IntelliJ’s built-in git GUI.
I don’t understand why people use command line only. Sure, learn the commands so if you need to use them you can, but most GUIs are far more feature rich than command line. With IntelliJ, I can easily view differences before committing, have it do code quality scans, automatically clean up any code it can, more easily choose which files I want to commit vs the typical ‘git add .’ I see most people do with command line, have separate changelists when pair programming, and much more.
One argument that continually comes up is that command line is faster. I completely disagree. If I want to just commit the code without reviewing it, I can use 2 hot keys and the code is committed and pushed. But as I do a quick readthrough of all the code first and review issues from the code quality analysis it does take more time, but still less than it would to do comparable things with command line.
as an idiot, I tend to click around without thinking. You don’t need to understand what you’re doing as much with a gui. When I started using the command line I started having a lot less problems, lol
The IntelliJ merge UI is the only way I ever want to deal with merge conflicts. So much better than any of the alternatives I’ve tried!
I’m a heavy intellij user, but the git log UI always confuses me. When I open ‘git log’ via the action menu IntelliJ doesn’t focus my current branch. I am not sure if there’s some other menu I’m supposed to use to achieve that.
I do use the commit local changes, pull changes, merge branches functionality a good bit. My only feedback there is that I haven’t found a way to quickly commit changes without running git hooks. Each time it requires me to open up the gear icon and deselect ‘git hooks’. This is slower than using the command line where I can write
git commit --no-verifyand repeat the same command again and again. I know it’s a niche need, but it’s necessary for testing a rather archaic system we maintain.
Apart from the cli, gitk and git-gui are plenty good in my opinion, they could always be made better. And they are mostly always there with git Only thing I am miasing now is blame.
I use the TUI gitui Though I also use the git cli directly too, depends on what I’m doing.
I’m loving all of the TUIs cropping up lately. Thanks for sharing!
The number of Git front ends with proprietary licenses is too damn high.
I use a 50%-50% mix between
gitCLI and the built-in git tools in JetBrains IDEs.To be honest, I could quite easily get by with just the JetBrains GUI - they have a super sophisticated GUI that can easily handle things like interactive rebase, cherry-picking, etc + they have a great conflict resolution tool. I just use the cli every now and then if I want to get something done quickly while I don’t have an IDE window open.
This one. It’s sophisticated and easy to navigate.
I generally do conflict resolution in Jetbrains IDEs and everything else in CLI. Occasionally, I might commit from the IDE if I only want a single file.
I mostly use the CLI but when I used to use PyCharm the JetBrain git GUI was the shit. The closest to it in a standalone program I’ve seen is maybe sublime merge, which is also great.
No, I find typing faster than clicking and I’ve been using git for so long the commands are second nature to me.
What I prefer most about having a UI is the better sense of overview over the repository and it’s branches.
I find, when compared to people I’ve worked with that prefer plain git, that I’m much quicker at finding certain changes or seeing what is in which branch with GitExtensions.
Developing in a Windows environment, I generally prefer Git Extensions.
It doesn’t distract the eye with unneeded fancy and is very close to a command line git experience but still allows me a better visual sense of the repository and branches.KDE has a relatively new git tool named Kommit: https://apps.kde.org/de/kommit
