@fpar I respectfully disagree with you. For many of us, it is considered a good practice to keep the code repository clean of IDE-specific metadata, any IDE-specific metadata, period. I'm not saying you shouldn't place your project's IDE settings under version control. In fact, it makes a lot of sense to do so, provided you keep it in a separate repository. As a good rule of thumb: if the CI server doesn't need it to build, run, test or deploy the code, then it has no business being part of the code base.

And your claim that including .iml files "is recommended by the official documentation" is simply not true. As @smamontov already pointed out above, the documentation you referred to clearly started with the sentence "If you decide to share IDE project files with other developers...". (Emphasis mine.)

I was surprised and frankly disappointed when I suddenly saw this change after I had checked out a new .gitignore file from gitignore.io. Why does the burden of having to uncomment all that unwanted stuff suddenly have to lie with those of us trying to keep things clean and wanting to follow generally accepted best practices?

Judging from other responses in this issue thread alone, I'm clearly not the only one who disagrees with this change, which seems to have been prematurely made without a proper debate.

@joeblau Asking the developers to revert this change once again is probably too much to ask, but would you then please at least consider adding a parameter called "intellij_all" or something, so that people would have a convenient choice, without having to manually edit their .gitignore files, which would defeat much of the purpose of gitignore.io? That way, as soon as someone starts typing "intellij" in the field, both options will come up, immediately alerting the user that there is in fact a choice. Thank you in advance for considering my request and my apologies for coming off a bit cranky in this response. It's late.

Add *.iml to IntelliJ .gitignore #186

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions