The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
Same here. It's so easy to use and the icons in file explorer show you the state.
But there is (or was) a limitation on the number of modified icons that Windows could handle. A really small number like 16 or so. Installing another package first which also modifies the icons, you might not see the advantage of the icons, because they are listed but not shown when exceeding the limit. No error message either. Unfortunately I don't remember which version of Windows had this restriction.
I too use TortoiseGit (also Visual Studio), but for merging I've never found anything better than Beyond Compare.
"I intend to live forever - so far, so good." Steven Wright
"I almost had a psychic girlfriend but she left me before we met." Also Steven Wright
"I'm addicted to placebos. I could quit, but it wouldn't matter." Steven Wright yet again.
Me, too. I occasionally look around at the alternatives but I have found nothing that beats Tortoise Git in terms of ease of use, functionality, and integration with Windows. And I also prefer WinMerge (especially the new version) over Tortoise Merge.
I wish Tortoise Git were available on Linux, because I use that sometimes too. The best I have found so far on Linux is GitEye, which comes pretty close to Tortoise Git in functionality and style.
I learned using source tree, but have switched over to doing most everything except conflict resolution using the command line tools. For that, I like VSCode the best, over any of the side by side diff tools that I've used. I also prefer rebasing over merging whenever I can, but that's a team decision.
I've only ever used the GitHub Desktop UI. It's simple and easy to use for the most common git tasks and for the hard ones it can start up a git shell. Personally I just use a shell now though. Not because the GUI is bad or anything, but I was responsible for the repo on a project and found myself mostly in the shell so I'm just used to it now.
Not a UI, but a user interface all right: gitless.com I suggest checking it out, I'm not fully versed in it (yet), but so far, it seems like it greatly simplifies common uses cases.
Running it on Windows through WSL.
A mix of command-line & GitKraken. I'm not averse to Fork either - especially for those repos I have that are very large (they have 15 years or history, having been migrated from SourceSafe through Subversion and Mercurial to (now) Git).
Why migrate from Mercurial to Git? To take advantage of Azure DevOps availability in our (large) company rather than having to maintain a Mercurial server... And also because the writing on the wall is writ large at this point...
Java, Basic, who cares - it's all a bunch of tree-hugging hippy cr*p
Bash is by far the most straightforward interface.
For visualization of branches, source tree does a fine job.
Bash can be very fast though, especially if you use aliases to shortcut common commands.
Shells are interfaces for users in case anyone is confused by my response.
GUIs are a specialization of UIs also 😏