[shkkmo]

I tried and failed to find a quality git gui for linux, (coming from SourceTree on OSX). I tried a number and they either had awful UI, lacked functionality, or were too buggy.

In the end I ended up paying for a license to GitKraken and am quite happy.

[merb]

basically using a gui for git is not a good practice. most stuff is cluttered together and hard to find. even in sourcetree, stuff that is important is just not good. (I used sourcetree heavily in the past) I moved on from graphical git clients and I'm now way more happy and more productive on the cli. the only thing which I would miss on linux is a graphical merge tool, that is as good as kaleidoscope even on windows it's hard to find an equally well tool for the same price (there are good ones, but are way pricier)

[shkkmo]

I use both gui and command line. Which one varies depending on the task. Quickly checking the working directory state and committing a couple of changes is much easier for me in a GUI. Complicated resets, checkouts, rebases and queries are much easier with the command line.

Edit: I find using a GUI to view the state of a git repo reduces the amount of mental space and energy I need to devote to this information.

[s73v3r_]

"basically using a gui for git is not a good practice. "

That is absolutely silly and completely false. I use SourceTree every day and have no issues whatsoever. I'm just as productive as anyone on the CLI, as 95% of actions are the basic pull/commit/push type stuff.