Currently our PR’s will be blocked if the code coverage is below 80%.
Just as with issues, we can mark them as “won’t fix”, or “false positive”, is there a way to do this with code coverage reporting from sonarqube.
I guess the context is that we are considering blocking merging till all the sonarqube issues are resolved. e.g. with code smells you could mark them as won’t fix, or false positive, and this can stop the quality profile from failing, but not so with code coverage
This is a topic we are thinking about for the future.
Would you mind sharing more about your use case? Do you have specific reasons to occasionally bypass the level of coverage that you expect from your PR?