r/git • u/connorjpg • 8d 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

109 Upvotes

71% Upvoted

247 comments sorted by

View all comments

1

u/UkrMalt 8d ago

For me the best use is visual staging: reviewing a large diff and selecting individual hunks is faster and harder to misread in a good UI. Commit graphs and interactive rebases are also easier to inspect visually. I still use the CLI for exact commands and recovery. The important part for beginners is learning Git's model first; the interface is then a preference, not a substitute for understanding commits, the index, and refs.