Your preferred Git UI (if any)?

[MehreenTahir]

I usually work with visual studio code but I'm afraid that doesn't fall under Git UI but more bash. On the contrary, GitHub Desktop serves the purpose quite well.

[Mircea Neacsu]

TortoiseGit with WinMerge for diffing. Started using it from the time of TortoiseCVS and never changed. Love to see the stuff I forgot to commit by just opening File Explorer.

Mircea

[MSBassSinger]

Team Explorer in Visual Studio.

[Andy Brummer]

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.

Curvature of the Mind now with 3D

[Jon McKee]

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.

[Maximilien]

tortoise, mostly because I used it for SubVersion. I installed/tried/uninstall many git tools. We started using Azure DevOps, so I will try the integrated VS tools

I'd rather be phishing!

[MarkTJohnson]

I happily pay for the individual license of GitKraken and with the features added in version 7 it is better than ever. You can link your Issue Tracker to Kraken and update stories from inside Kraken, create branches based off the story name, even create stories inside the tool.

[Jacquers]

Sourcetree. It has the Git flow workflow which we use.

[Efe Erdogru]

Tortoise Git

[GuyThiebaut]

Git Extensions - but I only use Git on home projects.

“That which can be asserted without evidence, can be dismissed without evidence.”

― Christopher Hitchens

[ISanti]

Visual Studio is not the best UI, but it is the one that best integrates code editing with Git version control.

Sorry for my bad English

[Jacquers]

Visual Studio Code's Git Lens is useful as well.

[Martin Hart Turner]

Exactly the same here, a great implantation and so easy to use.

[Mark Jerzykowski]

I have used many a git client but for the last year have been using fork Fork - a fast and friendly git client for Mac and Windows[^]. You have to pay for it these days but it’s well worth it in my opinion.

[OriginalGriff]

It does the job, and it stays out of the way. What more do I want? :laugh:

"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony "Common sense is so rare these days, it should be classified as a super power" - Random T-shirt AntiTwitter: @DalekDave is now a follower!

[Member 9167057]

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.

[Riz Thon]

Same here. I added Control TortoiseGit from within Visual Studio[^] to access it fast.

[User 13269747]

I use the cli that comes with my distro. On the rare occasion I work on our one and only Windows product, I use git bash.

[fd9750]

Yep, by far the most logical and intuitive combination. I have used multiple others and they do not even come close.

[Jim Knopf jr]

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.