exclude compiler.xml and artifacts when using Gradle #3236
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In our IntelliJ projects where we are using Gradle, the file .idea/compiler.xml and files inside the .idea/artifacts folder are automatically generated by IntelliJ based on the Gradle build model.
Reasons for making this change:
Automatically generated files should be ignored in version control.
I did comment out my changes though, as the existing Gradle/Maven related ignore rules are commented out as well.
Links to documentation supporting these rule changes:
https://intellij-support.jetbrains.com/hc/en-us/articles/206544839?page=3#comment_360000710180
Answer of Serge Baranov to my comment:
The files generated on import and not having any manual customizations can be safely excluded from the version control.