DEV Community

loading...

Which Git Tool do you use in your work, Git GUI, Git Bash, Git CMD ?

Shaiju T
I am a Full stack .NET Developer, I like to work with C#, Asp.Net Core, SQL, Mongo DB, Azure, JavaScript... Always eager to learn new technologies. I am here to share, ask & eventually learn.
・1 min read

While working with Git there are many options like Git GUI, Git Bash and Git CMD.

I feel Git GUI like SourceTree and GitHub Desktop are more easy to use than Git Bash or Git CMD.

Why you would prefer Git Bash or Git CMD over Git GUI ?

Which Git Tool do you use in your work to increase your productivity ?

Let's discuss 😄

Discussion (13)

Collapse
moopet profile image
Ben Sinclair

You bring up Git Bash and Git CMD so I assume you're targeting Windows users?

When I'm on Windows I use command-line git from WSL or I shell into a different system which has the full toolchain.

I don't use the GUIs, though I've given them a go. It's not that I'm some kind of hipster, I genuinely find it more difficult to understand visual representations of things than a text description.

Also I script the crap out of everything :P

Collapse
ahferroin7 profile image
Austin S. Hemmelgarn

None of the above.

When I absolutely need to use it from Windows, I use it under WSL so that I actually have a complete environment and full access to both everything git itself can do as well as full functionality of a properly managed UNIX shell environment (ZSH in my case, but that's orthogonal to this).

Otherwise, I just open a terminal emulator and start using it directly.

I have some integration with my shell (displays the branch name, if there are changes or not, and if there's anything stashed or not for the repository I'm currently in) and my editor (displays branch name and whether the file I'm working on has changes relative to the branch), but those are honestly just convenience items that I don't even technically need.

In my experience, the GUI options don't really add much unless you don't have a complete understanding of how VCS works in general or have serious issues mapping mentally from the textual output to the actual DAG structures and the transformations on them that are performed by Git. Neither is the case for me though, so there's not really any benefit to me using a GUI.

Collapse
kendalmintcode profile image
Rob Kendal {{☕}}

Colour me contrary, but I generally don't like CLI and other command line things. I find GUI-based things much easier to track all the moving parts.

So, with that in mind, I use a few:

  • Fork
  • And the official GitHub Desktop app. It's really nice and clear for fairly high-level git things
Collapse
shaijut profile image
Shaiju T Author

Yes GUI is much easy to track.

Collapse
choroba profile image
E. Choroba

I use the git command line interface combined with gitk (tk application to show the graph) and magit - Emacs interface to git. git add -p is so much easier with magit!

Collapse
jeffjadulco profile image
Jeff Jadulco

I mainly use Git Fork, it's simple and clean. But when I need to execute custom commands that you don't commonly find in Git Clients, I use Git Bash.

Collapse
shaijut profile image
Shaiju T Author

Git Fork is new to me. Thanks :)

Collapse
alphaolomi profile image
Alpha Olomi

GitKraken, Github desktop and the CLI with custom bash alias and functions

Collapse
emperorkonstantin profile image
Konstantin Anthony

Git that's integrated in my IDE, and occasionally git bash. It really depends, sometimes Sublime Merge.

Collapse
shaijut profile image
Shaiju T Author

Yes for me integrated in IDE like Visual Studio, is much easy to use. Thanks :)

Collapse
ankitbeniwal profile image
Ankit Beniwal 🙂

I usually go with GitKraken when I am not using command line.

Collapse
shaijut profile image
Shaiju T Author

GitKraken is new to me. Thanks :)

Collapse
shaijut profile image
Shaiju T Author • Edited

Some differences I found in StackoverFlow.com.