Unlike Netbeans, in Jetbrains IDEs, the setting files related to user and team are mixed in the same folder that makes it tricky when you need to push them to git.
There is a number of sample git ignore files for these IDEs and https://intellij-support.jetbrains.com/hc/articles/206544839 page on git site.
However, after using them for a months we figure out that it is safer and actually more convenient to do the reverse. I mean ignoring all .idea
files and adding only team-related settings explicitly. (instead of adding all and ignoring some).
The main thing that can be shared among developers is code style configs. So, by using IDE auto-reformatting option all the team will follow a consistent style.
Besides that, the question is which other files are recommended to be included and not ignored? Why?
Answer: I came across with this: https://github.com/salarmehr/idea-gitignore
Jetbrains has some official guidance on which files should not be checked in, and which files should probably not be checked in, depending on your usage. According to that page, you should check in all files in the .idea
directory except:
workspace.xml
tasks.xml
And probably also:
dictionary
subdirectoryWhile the particular answer may depend on your team's particular practices, in my experience, following that guidance generally results in correct separation of user settings and shared project configuration.
Some examples of files that should be shared, according to this guidance:
ant.xml
, which, if you use Ant to build your project, points IDEA to your build files and configures properties that should be used to build.vcs.xml
, which specifies the Version Control configuration for your projectencodings.xml
, which specifies how IDEA should treat the text files in your projectmodules.xml
, which points IDEA to each of your project's module configuration files, which should also be shared in your VCS.runConfigurations
subdirectory, which tells IDEA what it needs to do to run your applicationcodeStyleSettings.xml
, which, as you have alluded to, puts your whole team on the same page in terms of automatic code formattingDepending on your team's usage, there may be more or less, but those are some of the biggest examples.