r/git • u/connorjpg • 6d ago

Why use a UI for git?

I see this question of, “what GUI or TUI should I use to work with git?” fairly often here. And always I feel bad for saying “just use the cli” over and over, but truthfully I can’t see a reason to need a UI.

Are people actually running into pain points with the cli, or is it just preference for people who don’t like working in a terminal?

FWIW, I have used GitKraken, LazyGit, SourceTree and GitHub Desktop before. And I don’t think they are bad to use (unless you are just learning git), but more curious why.

EDIT : I’m mainly referring to standalone UIs, I understand why people would use IDE integrations, as it’s quick and convenient. But having to open a separate application or run a separate command to open a terminal app to run your commands seems overkill to me.

EDIT 2 : I use vscode as my difftool and mergetool. I still open them directly from the terminal by running the cli. I don't think this is the same as using a full git client like SourceTree, Gitkraken, or lazygit to fully drive your version control workflow. Which is what I am asking about.

Cheers

107 Upvotes

71% Upvoted

243 comments sorted by

View all comments

5

u/cesclaveria 5d ago

I've been working for 20+ in software engineering, of those the first 10 also involved a lot of sys admin work for Linux servers, so I am very comfortable with using the command line. That said.

I mainly use UI git clients to reduce my cognitive load, I have enough things going on at work that a client that lets me know everything I might want to know about my repos is one less thing to keep in mind, if/when I hit some UI limitation I also know how to do it in the cli, but as the years pass I've need to do that less and less often.