I'm aware that PhpStorm does not currently support git submodules, but I want to make sure I understand what exactly that means. I conducted a simple test and want to make sure I'm not missing something.
Is it correct to say that PhpStorm interprets git submodules correctly but that there is no interface to manage them?
I find it rather convenient to use the Command Line Tools Console to manage the submodules. For my quick test, I cloned a git project which has several submodules. I then updated them through the commandline tools console using my git alias. PhpStorm asked me if I wanted to add all the files to the main repository but I declined. I thought this is where things were about to go wrong, but I believe it was simply a false positive because once declined PhpStorm did not persist with wanting to add the files. Looking at the repository through PhpStorm, everything looks correct.
Taking it one step further, I used the command line tools console to add a submodule to the repository. I was again confronted with a pop-up asking me if I wanted to add all of the new files to the repository. I once again declined. And again, PhpStorm appears to interpret everything correctly because it shows the .gitsubmodule file and submodule directory as local changes they need to be committed.
I'm assuming here that committing a submodule addition through the PhpStorm interface will create a reference and not actually add each individual file within that directory to the main suppository…correct?
Sorry for the long explanation but I just want to make sure I understand it correctly. It was (?) the only doubt holding me back from adopting PhpStorm is my new weapon of choice.