Current Method for Disabling PR Decoration in Azure DevOps?

SonarQube Cloud
, ,
1

How do I disable PR comments at the Enterprise or Organization level for Azure DevOps repos? It’s been well documented here that PR decoration is spammy on Azure DevOps. We just set up SQ Cloud and now Developers have to click 50 ‘Resolve’ buttons for some PRs.

The UI has changed since the screenshots & info from the time this was first reported in 2019. Currently, if you want to see the settings for a project, you’ll have to go to <project page> → Administration → Restore Access. (On the first repo, this worked fine. The second time I tried it, I had to repeat the process a few times before the page re-rendered (flickered) and the hover menu that appears on Administration mouseover updated.)

image
image269×104 4.9 KB

After restoring access, I could access PR settings like I’ve seen reference multiple times - Administration → General Settings → Pull Requests

image
image1007×655 63.9 KB

However, there are no settings for PR decoration and everything is blank anyway. But that’s kinda fine; I have zero desire to administer this for each repo. How do I disable PR comments at the Enterprise or Organization level for Azure DevOps repos?

Resolution Levels:

Ideal behavior is a single summary comment (like what’s available for GitHub).

Behind that is turning it off PR decoration for the entire org/enterprise.
    The info being decorated is already where it’s supposed to be - SQ. I saw a reference to using a bogus PAT, but can’t find that post again now.

Undesirable, but at least functional, is turning off PR decoration for each repo (SQ project).
    That’s an administration nightmare, but better than having Devs click 50 ‘Resolve’ buttons in ADOS - one for each comment on the PR.

Unfathomable seems to be where I’m currently at - either there’s not a way to do this or I don’t yet know what that reason is.

Does the ideal scenario or the one behind that exist?

2

Hi,

These are your best options. Having a bogus or expired organization-level PAT will indeed block PR decoration. It will also prevent you from importing addition repositories as your company bootstraps new projects. (You could, of course, swap in a valid PAT briefly when you need to set up new projects, and then swap it back out when you’re done.)

Note that it should be possible to script deactivation of PR decoration at the project level with the APIs. The best way to master the API is to perform the desired action via the UI and eavesdrop to see which calls the UI made to accomplish the action.

You may also find this guide helpful.

 
HTH,
Ann