But why would you use Git instead of Mercurial, Subversion, Fossil or Darcs?
The Windows installer should install Git-Bash which gives you a shell command line in Windows.
Windows already has cmd, the PowerShell and (optionally) a native Microsoft version of the bash. I advise everyone to stick with the native solutions instead of imposing a GNU simulation layer which can't speak NTFS.
Your challenge for now is to build a habit around using Git… even when you don’t need to.
This is a really bad idea. A VCS is overkill for most projects, especially Git is. You'll find yourself having to work around problems which you wouldn't have without Git much too often. A VCS - any VCS - is a tool to solve actual problems. If your reason to use Git is to use Git, you make a huge mistake which you'll regret rather sooner than later.
That said, if you absolutely want to use Git "because you can":
No Git GUI will ever expose all the functionality of Git.
GitKraken is sufficiently OK, minus the giant problem that it is based on Electron.
I agree. Honestly, I use Git myself to practice the workflow, not really much to solve actual problems.
I also find it extra satisfying to git commit and git push, so that's a plus. I guess it's more of the experience for me rather than the practicality of it.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
But why would you use Git instead of Mercurial, Subversion, Fossil or Darcs?
Windows already has
cmd, the PowerShell and (optionally) a native Microsoft version of thebash. I advise everyone to stick with the native solutions instead of imposing a GNU simulation layer which can't speak NTFS.This is a really bad idea. A VCS is overkill for most projects, especially Git is. You'll find yourself having to work around problems which you wouldn't have without Git much too often. A VCS - any VCS - is a tool to solve actual problems. If your reason to use Git is to use Git, you make a huge mistake which you'll regret rather sooner than later.
That said, if you absolutely want to use Git "because you can":
GitKraken is sufficiently OK, minus the giant problem that it is based on Electron.
I agree. Honestly, I use Git myself to practice the workflow, not really much to solve actual problems.
I also find it extra satisfying to
git commitandgit push, so that's a plus. I guess it's more of the experience for me rather than the practicality of it.