Create .codacy.yaml to not analyse JSON files #9
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.
Hey there @pedrocodacy from the Codacy dev team here 👋
I've noticed through internal monitoring of the product that you have this repo integrated in our product and are getting 45-60 minutes analysis times.
Looking through your configuration, I can see that you have already disabled all code patterns that analyze JSON files, which seems to indicated that you are not interested in analyzing these.
One detail that is relevant for your usage of the product is that Codacy will still run a bunch of background code metrics calculations on JSON to calculate number of lines of code in this case. Given the large amount of JSON files in this repo, this ends up severely hurting your analysis times.
This PR introduces a Codacy configuration file at the root of your repo, ignoring these files.
From tests I did with a forked version of this repo, I got analysis times of commits to drop to under 15 minutes.
Have a nice day 👋 🌻