this post was submitted on 20 Jun 2023
47 points (100.0% liked)
Programming
13376 readers
1 users here now
All things programming and coding related. Subcommunity of Technology.
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I use IntelliJ's built-in git GUI.
I don't understand why people use command line only. Sure, learn the commands so if you need to use them you can, but most GUIs are far more feature rich than command line. With IntelliJ, I can easily view differences before committing, have it do code quality scans, automatically clean up any code it can, more easily choose which files I want to commit vs the typical 'git add .' I see most people do with command line, have separate changelists when pair programming, and much more.
One argument that continually comes up is that command line is faster. I completely disagree. If I want to just commit the code without reviewing it, I can use 2 hot keys and the code is committed and pushed. But as I do a quick readthrough of all the code first and review issues from the code quality analysis it does take more time, but still less than it would to do comparable things with command line.
The IntelliJ merge UI is the only way I ever want to deal with merge conflicts. So much better than any of the alternatives I’ve tried!
I'm a heavy intellij user, but the git log UI always confuses me. When I open 'git log' via the action menu IntelliJ doesn't focus my current branch. I am not sure if there's some other menu I'm supposed to use to achieve that.
I do use the commit local changes, pull changes, merge branches functionality a good bit. My only feedback there is that I haven't found a way to quickly commit changes without running git hooks. Each time it requires me to open up the gear icon and deselect 'git hooks'. This is slower than using the command line where I can write
git commit --no-verifyand repeat the same command again and again. I know it's a niche need, but it's necessary for testing a rather archaic system we maintain.