Can you tell me what specific actions you’re taking to rebase the PR that “fixes” the issue? Is this something within your CI, or a command you’re running in a relevant branch? With this info, I think I can pass this onto our developers.
asking mergify to do it with a @Mergifyio rebase PR comment
The rough idea we have is that consecutive analysis runs on PRs are accumulating differently than before, so then it makes sense that a rebase “fixes” that since it rewrites history and disconnects the PR from previous runs.
As far as SonarCloud is concerned, it shouldn’t be “accumulating” anything – each analysis will result in a brand new set of changed lines/files being reported to SonarCloud that replaces the previous one.
I should have asked before – but it would be helpful to see DEBUG logs (sonar-scanner -X) from a run before and after the rebase.