Problems with Git integration
After a break of several weeks and a change of computing platform I started using IntelliJ 2018.2.2 and now 2018.2.3 on a new MacBookPro.
I've noticed some issues with the Git integration that I had not seen before in previous IntelliJ versions.
* Changes are not always marked in the gutter, even when the filename is shown in blue
* When trying to commit my changes, I sometimes get the message that there are no changes to commit even though there are
* I wanted to check the history of a particular file in my project in Git - and the button to do so is disabled.
The changes in those files are correctly picked up by SourceTree or commandline Git, and committing from commandline or SourceTree is possible when IDEA claims there are no changes.
IntelliJ version:
IntelliJ IDEA 2018.2.3 (Ultimate Edition)
Build #IU-182.4323.46, built on September 3, 2018
Licensed to Tim van der Leeuw
Subscription is active until May 12, 2019
JRE: 1.8.0_152-release-1248-b8 x86_64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
macOS 10.13.6
Git version:
$ git --version
git version 2.15.2 (Apple Git-101.1)
(SourceTree has it's own version of Git which is 2.17.1 but when switching that to the system-wide version 2.15.2 everything still works as expected).
MacOS version: 10.13.6
The project is a Groovy / Grails project. Some files that I edit are not part of the project but are under version control. However that doesn't seem to make a difference here.
There is no problem with the communication with Github - pushing and pulling all works. It is just the detection of changes to files that seems broken.
Please sign in to leave a comment.
Please make sure that the mappings in the Settings | Version Control use explicit project path and not just a generic <Project>.
if it is not the case, please submit an issue to the https://youtrack.jetbrains.com/issues/IDEA with logs attached
It currently says <Project> there. This was set after checking out from Github and importing - it was not set by me.
Besides, the way that <Project> is described makes it sound like it is exactly what should work -- and it kind of works, just erratically at the moment.
That's a problem which I have not yet had before.
I will change this and see how the Git integration behaves today but that still sounds to me like there's a bug in there, somewhere, if the way that IntelliJ imports the project is not how you say it should be and if the <Project> generic entry doesn't do properly as described.
It seems that with that change to the project configuration, the Git integration works more stable again.