Aibolit would be more useful if project can control the minimum score to include CLI into build pipeline. I'd suggest adding additional configuration parameter to require minimum score instead of zero to fail the build, e.g. aibolit --min-score=5 exits with ok=0 if score <= 5, and fail (exit status 1) if > 5.
This is another way to get rid of such behaviour. Now we can just ignore pattern for function or class.
Should we implement it? @yegor256 @acheshkov Seems we have solved it with @SuppressWarning feature
Aibolit would be more useful if project can control the minimum score to include CLI into build pipeline. I'd suggest adding additional configuration parameter to require minimum score instead of zero to fail the build, e.g.
aibolit --min-score=5
exits with ok=0 if score <= 5, and fail (exit status 1) if > 5.