It would a way to customize the analysis report like dev can with a linter for example:
This configuration file would define :
- ignored warnings or pitfalls
- possible parameters if a pitfall or warning is using any (eg: difference between latest release and codemeta version < 2 patch ; could be 1 or 10).
- exclude files
This configuration is also a way for us to handle different usecases. For example, we may not want the github action to detect the same pitfalls/warnings if the action is run on a prerelease state versus a dev/unstable one.
unstable/dev state would use a more tolerant configuration than the prerelease one.
It would a way to customize the analysis report like dev can with a linter for example:
This configuration file would define :
This configuration is also a way for us to handle different usecases. For example, we may not want the github action to detect the same pitfalls/warnings if the action is run on a prerelease state versus a dev/unstable one.
unstable/dev state would use a more tolerant configuration than the prerelease one.