|
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.
|
|
|
|
|
I use SourceTree as it supports all Git commands that I know of in an intuitive enough interface.
I like that I can have multiple Git repositories open in tab pages at the same time and that I can categorize all my repositories in folders.
For some small projects or ad-hoc stuff I also use Visual Studio, sometimes next to SourceTree.
Especially blaming and seeing the history of a file works well in Visual Studio.
I also sometimes use Visual Studio to connect to Azure DevOps repositories, only to manage them using SourceTree once they're cloned to my machine.
I've used the GitHub GUI for GitHub projects, but I'm not a fan.
The SourceTree / Visual Studio combo works great for me
|
|
|
|
|
SourceTree 1.10. Tried 2.x and 3.x and upgraded them back to 1.10.
|
|
|
|
|
I've used the Github GUI as well as Visual Studio. VS has been the primary for the last year or so, and it's worked well.
|
|
|
|
|
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.
|
|
|
|
|
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
|
|
|
|
|
Exactly the same here, a great implantation and so easy to use.
|
|
|
|
|
|
Yep, by far the most logical and intuitive combination. I have used multiple others and they do not even come close.
|
|
|
|
|
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.
Cheers,
Mike Fidler
"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.
|
|
|
|
|
Heard many good things of it but it's paid and I'm a cheap bastard
Mircea
|
|
|
|
|
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.
|
|
|
|
|
Team Explorer in Visual Studio.
|
|
|
|
|
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.
|
|
|
|
|
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!
|
|
|
|
|
Sourcetree. It has the Git flow workflow which we use.
|
|
|
|
|
|
Git Extensions - but I only use Git on home projects.
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
|
|
|
|
|
Visual Studio Code's Git Lens is useful as well.
|
|
|
|
|
|
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.
|
|
|
|
|
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.
|
|
|
|