[_virtu]

The commit workflow was what kept me locked in to the ecosystem for so long. LazyGit was so good that it convinced me I didn’t need JetBrains anymore. If you love the workflow with JB for commits check out LazyGit. It’s a TUI so you can use it in any editor without much friction.

[KptMarchewa]

I'm kinda reading this with disbelief. Are there people whose primary use case for IDE is... git gui?

[jghn]

I do almost everything git manually at the CLI. But the Jetbrains IDEs have a fantastic GUI git merge tool, and I also like the local git diff UI. Add in integrated blame mode, ability to pull up version-diff files, and that sort of thing.

It's not part of my daily driver toolbox, but they do get used a lot by me.

[calderwoodra]

Remember this when you're thinking about the average commenter's opinion on anything technical.

[conradfr]

Jetbrains' implementation is (was?) just that good, yes (combined with local history).

[brianpan]

I think you're thinking about git as a separate thing from the IDE.

I love using IJ + git because there are no seams in between edit and commit. For instance, with IJ, I could easily split every other line of a change into separate commits.

Maybe there's a way in git to stage only certain parts of a diff, but I'd have to go an learn another flag or command that I'm going to forget by the next time I need to do it again.

Also with IJ, I just glance at my main branch tab and the highlighting tells me what commits aren't in my checked out feature branch.

Two small examples but there are many more and it adds up.

[_virtu]

That's not the only reason I was using the tooling at the time. Specifically everything else regarding the JetBrains ecosystem kept me hooked, but when I was looking to replace what I liked in JetBrains with other tooling the last piece of the puzzle was replacing the git workflow.

[ryanlitalien]

I've been using their git diff/checkin tools built into RubyMine since I started with git. Going on about 12-13 years now. Their conflict resolution UI is so much easier than editing text contents between the >>>>s and <<<<s.

[midasz]

To be fair, VS Code git implementation is really off-putting if you've used something good.

[insane_dreamer]

Honestly, the git implementation in PyCharm is better than any git app I've used, including lazygit (which I like and is my go-to when not in PyCharm).

[jgalt212]

Git is just that bad, huh? The best backhanded endorsement of mercurial I've seen so far.

[notpushkin]

Or if you prefer a GUI (still separate app, so works anywhere, too): https://git-cola.github.io/

[shunia_huang]

Graphical interface won't work well inside WSL, that's why I dropped my subscription on GitKraken and start using lazygit. lazygit simply works in almost any environment, and it works extremely well even if you are not into terminal stuff.

[gizzlon]

Just found LazyGit as well. it's amazing!

Also like Sublime Merge, if you want a GUI (paid though)

[nikanj]

Fortunately JB broke that addiction for my by first moving the commit dialog behind an option, and then removing it completely. If I have to learn a new workfrow, I might as well learn a new tool

[conradfr]

Currently the plugin version still works but they made it clear it will be unmaintained in the future.