It appears that individual issues that SonarCloud raises on pull requests can be resolved in the UI as “won’t fix” or similar. We want to do the same thing for code coverage: some lines are legitimately uncovered but zero risk from any practical perspective and should be exempt. I have seen documentation around code comments to ignore sections, but that feels like overkill. Is there any way to mark a build as “reviewed and acceptable,” effectively?
Welcome to the community!
Sorry, but there just isn’t a way to mark duplications or (lack of) coverage Won’t Fix.