@ geometry dash lite: This features sounds amazing. Hope that it will be considered.

For future searchers, adding --quiet to suppress your warnings is the easiest way to do this.

Yes eslint is it's own step and we output the xml. The problem arises when you set something to warn rather than error. The basic use case being you want to deprecate something but you can't really do it all in one fell swoop. The warnings show up as red failures in the error reporting in circle though so the warn feature of eslint is pretty much useless for circle since it can generate so much noise.

Thanks for your idea! How do you currently run eslint? Would it be possible to separate it out into its own build step so that the output doesn’t mix up with the rest? Are you reporting eslint errors via JUnit XML?