Azure DevOps PR decoration undocumented behavior?

[Fabrice_Bellingard]

@S.V.Groeneveld

On a large pull request there were 20 comments generated by SonarCloud, but when we navigated to the SonarCloud PR analysis page there were actually 75 issues found. And every PR build it would add a few new comments to the PR… Is there some undocumented max limit on the number of comments it can post on a PR?

I’m not aware of such limit. Maybe @Julien_HENRY can give more insights.

@S.V.Groeneveld

When we change the issue status within SonarCloud, it automatically updates the status accordingly in the Pull Request. But when we set the status in the PR to “WontFix” upon next build it will mark the issue in SonarCloud as “Fixed” (instead of “WontFix”).

When you say “when we set the status in the PR to WontFix”, you mean when you do it in Azure DevOps UI?

@S.V.Groeneveld

SonarCloud comments seem to be deleted from PR’s after resolving them. We never delete our manual comments, since this is making it difficult to read historical PR’s and understand the reason things got changed. Why is SonarCloud doing this?

I guess the idea is to not “pollute” too much the PR with useless comments (when issues are fixed, there’s no more problem). You would expect the comment to be set to “Closed”?