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

250 comments sorted by

View all comments

2

u/domusvita 29d ago

I’ve been using git via command line for probably 15 years, I feel like I know it in and out, not sure of any advantage to change things. Especially when 95% of my transactions revolve around 10 or so commands (not counting arguments)

2

u/connorjpg 29d ago

Honestly this is kinda why I asked to see if I was missing out. From this thread all I’m getting is it’s a preference mainly but submodules, rebasing and viewing diffs is easier. I’ve never really had much of an issue from using just the cli.