Fail if error count increases

[gregplaysguitar]

Firstly, thanks to the maintainer for the great tool - I've been using it to gradually chip away at several thousand TS errors in a reasonably large codebase, and it's really useful!

I wondered if you'd consider a stricter mode that enforces the error count, to ensure it goes down over time? I think this would make it easier to work with in a team, because right now even if a team agrees on the approach and direction, progress can still stagnate

The ideal workflow I'm imagining is

• run a command locally to update the suppressConfig as needed
• check in the suppressConfig file
• run in CI in a stricter mode, where the command fails if the suppress errors and counts per file don't strictly match the codebase

This means CI will fail in either of these scenarios

1. A change introduces new errors
2. A change addresses some errors, but doesn't also update the suppress config

I'd be happy to implement this, if you think it's a good idea?

[kawamataryo]

I have filed an application for reopening. However, the freeze is still not lifted..