Github check (Quality Gate of new coverage) fails after refactiong untested classes


(Enes Özel) #1

We’re actually using the new quality gate of new code coverage in our projects, and there we had to rename classes with too little test coverage. Now the check does not go through in GitHub, because it is recognized as new code instead of old changed code. We did not found any possibility to accept the new state in sonarcloud, just like it is possible for issues themselves by marking them as false positives or won’t fix. Is there a way to solve this problem apart from re-projecting and turning off check.