Bachmann1234
Failing on file where all changes are lines removal
Hi! We have PR where we only removed some lines of code, and no lines were added or changed. The file does not have good coverage and was written way before diff-cover was introduced into our CI, but it looks like it was detected as an uncovered and failed pipeline.
Do you know if this behavior is intended? IMO, when devs remove a bunch of code during refactoring in aged repos, it's not fair to ask them to cover all files uncovered before him just for deletion. But I understand an entirely valid point about failing the lint in cases where some lines were added or changed.
Also, is there any workaround to skip the linter using any keywords in the commit message?
So this behavior is a bit surprising to me. I would assume we only cared about additions/changes when looking at coverage or linting issues.
If you could construct an example repo showing this I can take a look and try and pinpoint exactly whats going on.
Right now there is not a workaround to skip the check
