I understand that this is “how it works” and there is nothing that can be done about it. This is explained here Issue management solution overview & SonarQube
During a pull request analysis, new issues on old code are not reported since only new code issues are reported. It means that the first analysis on the target branch after the merge may report new issues on old code that were not reported by the pull request analysis.
But do people just live with it or are there any possible mitigations? I find it quite embarassing a a time-waster to have a developer re-open their ticket right after merging because their merge cause the ‘main’ branch scans to fail.
Any workarounds?
Thank you
10.6
6.1.0
CFamily
