4 ms·
In my experience of using git integration features in IntelliJ, they are nice for simple tasks like quickly checking the status of a file or committing all the
by kelnage 8y ago
In my experience of using git integration features in IntelliJ, they are nice for simple tasks like quickly checking the status of a file or committing all the changes, but as soon as I need to do more complex tasks in git, I find the UIs either get in the way and slow me down or just aren’t fully featured enough to do what I need to do and I end up back on the command line. Hence why I always encourage newcomers to git to learn both if possible.
I do agree that git could certainly do with a more consistent command line interface - but I imagine that won’t even be considered until that next major version of git, if it ever arrives.
- Normal_gaussian 8y agoGit integration in IntelliJ is terrible IMO. It conflates staging and committing, and unstaging with reverting. I don't use it because it is a PITA, but what is even more annoying are the PR's from team members who do use it, which I have to send immediately back due to random files.
- korm 8y agoThe history features are incredible and also the only ones I use, eg diffing, showing changed dirs/files/lines, blame, file/dir commit history. I've never used it for anything else git related because the ui is strange.
- Rjevski 8y agoTrue, but frankly it is Git’s model that is broken, or at the very least overcomplicated. I do not care whether files are staged or not up until the point I actually want to commit, so personally the IntelliJ way of doing it is perfect.