Should we pass IDE parameters to VCS?

We work mainly in Java, using both Eclipse and Intellij as a team. We had a discussion in the team about assigning IDE settings (.iml, .project) to our git.

I am against this practice, but someone pointed out to me that it would be much easier for everyone to align with the same settings as the code and warning style.

And they showed me that modern browsers do a great job of separating specific local machines from specific projects.

Is there a reason why we should not comment on them?

+1
source share
1 answer

The only reason you could avoid the version of these files is if they contain developer-specific data (paths that are valid only for one developer, and not for others, what value matters only for one workstation, and not for others).

Any other files that are:

  • can be reused by any developer
  • help bring back an environment that can rebuild a program with identical settings

should be placed in VCS.
And including any IDE configuration files, as I mention in " Do you keep project files under version control? " Or " Which eclipse files belong to version control system .

+1
source

All Articles