PR doesn't show issue in SQ, issues are shown after merge in SQ

SonarQube Server / Community Build
1

Must-share information (formatted with Markdown):

  • which versions are you using (SonarQube Server v2026.2.1)

  • how is SonarQube deployed: zip

  • what are you trying to achieve

  • At the time the PR was merged, no Quality Gate issues were reported. However, after the merge, the issues became visible in the develop_enhancements branch that we merged to.

    These issues originated from the changes introduced as part of the same PR and were reflected only after the merge.

  • image
    image1271×625 95.5 KB

  • image
    image1275×604 150 KB

Do not share screenshots of logs – share the text itself (bonus points for being well-formatted)!

2

Hey @Kosta, this type of behavior often happens when the PR analysis cannot correctly detect the new code introduced/changed in the PR, and therefore doesn’t analyze the correct set of new code. Such new code added in the PR is detected via git, so the cause for this issue may be a lack of git data in the Scanner’s CI environment. Could you have a look at those analysis warnings that the PR analysis page is reporting? Those are also visible in the analysis logs, at WARN level. Do you see any warnings about git/SCM/shallow clone/missing refs?