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.
I am a Full stack .NET Developer, I like to work with C#, .Net Core, SQL, Mongo DB, Azure, JavaScript , Angular...
Always eager to learn new technologies. I am here to share, ask & eventually learn.
I'm a Systems Reliability and DevOps engineer for Netdata Inc. When not working, I enjoy studying linguistics and history, playing video games, and cooking all kinds of international cuisine.
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.
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!
I am a Full stack .NET Developer, I like to work with C#, .Net Core, SQL, Mongo DB, Azure, JavaScript , Angular...
Always eager to learn new technologies. I am here to share, ask & eventually learn.
I am a Full stack .NET Developer, I like to work with C#, .Net Core, SQL, Mongo DB, Azure, JavaScript , Angular...
Always eager to learn new technologies. I am here to share, ask & eventually learn.
God made the integers, all else is the work of man. 👋- I'm a web and software developer- I like TypeScript, Rust, GraphQL, and GNU/Linux.- Shippin' it! 🚢
I am a Full stack .NET Developer, I like to work with C#, .Net Core, SQL, Mongo DB, Azure, JavaScript , Angular...
Always eager to learn new technologies. I am here to share, ask & eventually learn.
I am a Full stack .NET Developer, I like to work with C#, .Net Core, SQL, Mongo DB, Azure, JavaScript , Angular...
Always eager to learn new technologies. I am here to share, ask & eventually learn.
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
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:
Yes GUI is much easy to track.
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.
I use the git command line interface combined with gitk (tk application to show the graph) and magit - Emacs interface to git.
git add -pis so much easier with magit!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.
Git Fork is new to me. Thanks :)
GitKraken, Github desktop and the CLI with custom bash alias and functions
I usually go with GitKraken when I am not using command line.
GitKraken is new to me. Thanks :)
Git that's integrated in my IDE, and occasionally git bash. It really depends, sometimes Sublime Merge.
Yes for me integrated in IDE like Visual Studio, is much easy to use. Thanks :)
Some differences I found in StackoverFlow.com.