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.
Referring to the following:
https://intellij-support.jetbrains.com/hc/en-us/articles/206544839-How-to-manage-projects-under-Version-Control-Systems
There's two types of files here:
.iml files, which we don't need (we're a Maven-based project)
.idea/... files, which it does recommend sharing
This removes all of them. Why? (a) It makes the project less IDE-independent, since we have IntelliJ files in the repo; (b) they cause annoyance when something changes for no good reason; (c) given the Maven configuration in pom.xml, it should autogenerate anyways.
As such, remove them and add them to the gitignore. If this becomes a problem, we can just allow them back in.
Possible problems with this:
However, IntelliJ does seem able to regenerate everything, which is why I'm not too worried.