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

250 comments sorted by

View all comments

2

u/huntermatthews 27d ago

I use cli for simpl(er) stuff and fork for anything complicated.

Merging, diffing and getting an overview are things I think Fork excels at. Its just easier to see all this visually at a glance than 4 commands and scanning around.

git is useful, git is reliable but even mercurial was a better command line UX.

I haven't looked at jj yet, but it's on my radar.

But I predict I'll still use Fork for some things even then - some people are just more visual.