New inspection level - SKIP about scapegoat HOT 3 OPEN

It feels like duplication to me.
The use case when one wants to see the issue in the output but not break the build is covered by INFO.
If one would not like to see the issue in the report can be achieved by disabling the inspection.
Do I miss a scenario?

from scapegoat.

You are right. My point is that the notion of disabling the inspection could be replaced with a new level.

This way we wouldn't need to develop and maintain two separate sets of configuration properties which overlap. E.g. we currently have default values for levels, but no support for a inspection to be disabled by default, etc.

from scapegoat.

Oh, yes, I see your point.
My thinking led me to the idea of having both, the list of disabled inspections and the new inspection level. What you say is about replacing the disabled list with the inspection level.
It might also play well with the configuration file approach form #439

from scapegoat.