SonarQube Cloud is decorating already-merged GitHub PRs weeks after merge without new commits. Example: exasol/pytest-slc#28 was merged July 30 2026, but sonarqubecloud[bot] created a new PR analysis today. Why does this happen?
The analysis was updated again yesterday 
Hi,
was merged July 30 2026, but
sonarqubecloud[bot]created a new PR analysis today. Why does this happen?
SonarQube Cloud is decorating the PR each time the branch is scanned. This is expected while the PR is open in DevOps; however, I’m not sure if this is intended behavior for when the PR is closed, so I’ve flagged this for further investigation by our engineer team.
Hi @kratz00
On our side, we publish the PR decoration after each analysis, despite of the PR status - typically closed PRs aren’t analyzed.
Here, it seems that the branch has been reanalyzed, and hence the decoration
HTH,
Anita
Thanks for looking into this. The PR has been merged weeks ago, the branch was deleted at the same time, so why would the PR/branch be reanalyzed multiple time since then?
Hi @kratz00
Could you confirm that there is no rouge GH Action running somewhere for this PR? On our side we can see that an analysis has been run, and in such case the PR decoration is expected