I also would like to see overall code conditions enforced for PRs from SonarQube, including PR decorations. A developer could delete all unit tests except those supporting his diff and Sonar’s quality gate would still pass their PR, which is quite problematic for automated PR quality enforcement.
Other sonar competitors like qlty.sh allow us to enforce “overall coverage” on PRs easily to ensure individual PRs do not decrease overall coverage even when the minimum diff coverage is met:
The linked issue for ratcheting conditions is ~60 votes which is even more than some of the issues listed in the “Coming Up” section. Is there something else holding the PMs from prioritizing this?