我们应该在VCS中提交IDE设置吗？ [英] Should we commit IDE settings in the VCS?

问题描述

我们主要使用Java，在团队中使用Eclipse和Intellij。
我们在团队中讨论了如何在我们的git上提交IDE设置（.iml，.project）。

We're working mainly in Java, using both Eclipse and Intellij in the team. We had a discussion in the team about committing IDE settings (.iml, .project) on our git.

我反对这种做法，但有人我指出，每个人都可以更容易地在代码风格和警告等相同的设置上进行对齐。

I'm against this practice, but someone pointed me the fact that would be much easier for everyone to be aligned on the same settings like code style and warnings.

他们也向我展示了现代浏览器做得很好将本地机器特定的东西与项目特定的东西分开。

Also they showed me as modern browsers do a good job of separating local machine specific stuff from project specific ones.

我们不应该提交它们吗？

Is there are reason why we shouldn't commit them?

推荐答案

您可以避免对这些文件进行版本控制的唯一原因是它们是否包含特定于开发人员的数据（仅对一个开发人员而非其他人有效的路径，某些值仅相关在一个工作站而不是其他工作站上。

The only reason why you could avoid version those files is if they contains developer-specific data (paths that are only valid for one developer and not others, some value which are only relevant on one workstation and not others).

任何其他文件：

• 任何开发人员都可以重复使用


• 帮助恢复一个能够以相同设置重新构建程序的环境

应该放在VCS中。

包括任何IDE设置文件，正如我在你的项目文件是否受版本控制？或哪些eclipse文件属于版本控制。

should be put in the VCS.
And that include any IDE setting files, as I mention in "Do you keep your project files under version control?", or "Which eclipse files belong under Version Control".

这篇关于我们应该在VCS中提交IDE设置吗？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！