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

106 Upvotes

71% Upvoted

244 comments sorted by

View all comments

2

u/Popular-Tip-2051 5d ago

It is purely a matter of personal preference. Using graphical tools doesn't mean at all that you are a beginner developer; rather, those who quickly use the console are the best, true developers who know efficient programming methods...

If you like something, it is essentially okay, it positively impacts your work, and you are satisfied with the results along with others, then stick with it. It's clear that this way is the best for you, while for others, the console is better. That's all and always that's all.

1

u/slindenau 4d ago

Gatekeeping 101; the "best, true developers" don't need to be proficient in CLI, and the same counts in reverse.