feat: Support nyc report --check-coverage

[isaacs]

No description provided.

[isaacs]

(force-pushed to fix lint error)

[coveralls]

Coverage remained the same at 96.399% when pulling 85e61ed on isaacs:report-and-check into 29e6f5e on istanbuljs:master.

[coveralls]

Coverage remained the same at 96.399% when pulling 8a30a52 on isaacs:report-and-check into 29e6f5e on istanbuljs:master.

[isaacs]

So does 2 approvals means it's cool for me to land this? I just realized I have write access on this org, but I don't wanna mess up any process.

[coreyfarrell]

So does 2 approvals means it's cool for me to land this? I just realized I have write access on this org, but I don't wanna mess up any process.

I just did it. For this PR a 'squash and merge' with the provided commit message was fine (you followed conventional-commit). I have no objection if you use 'squash and merge' for approved non-breaking changes as long as you make sure the commit message follows conventional-commit rules. For breaking changes I'd prefer that we have a chance to decide when those get landed.