Feature to have exit code 1 for info severity

[jakeleventhal]

I see there is the --error-on-warnings flag, but there's no way seemingly to error when there are info severity issues.

[ematipico]

I'm very concerned about implementing something like this.

We already emit some warnings that are outside of the linting/format scope, that's why we choose info as a backup to emit diagnostics.

If we decided to provide such an option, we can't emit info diagnostics anymore

[jakeleventhal]

How else do you suggest having a script that basically tells you "if you run the formatting you won't generate any diff". I think this is important to prevent people generating diff for files completely unrelated to their PR.

Example:

1. Person 1 creates a PR for feature A. No warnings or errors, but there are a number of info diagnostics that are not caught in CI. PR
   gets merged
2. Person 2 creates a PR for feature B. This user runs the formatter and now there is a bunch of diff on feature A.

If there were a way to prevent a PR from merging with info severity, then this is impossible. Manually checking git diff seems like a hack.

[ematipico]

Info diagnostics aren't meant to block the CI, IMHO. If you don't like the default severity of a rule, you can still change it via configuration.

[jakeleventhal]

the problem is there is an unknown number of rules that may be info severity. cannot possibly enumerate all of them