Pull Request Decoration Not Working on One GitHub Repo

[dswanson (Dan Swanson)]

Must-share information (formatted with Markdown):

• SonarQube Server Enterprise (2025.1)
• Docker
• I’m trying to get the PR decorator to post to the PR.
• About two years ago one of the repos just stopped getting a sonarqube post on the PR and I’m trying to figure out why..
  These are the keys I have in the sonar properties.
  sonar.projectKey=…
  sonar.exclusions=…
  sonar.cpd.exclusions=…
  sonar.sourceEncoding=…
  sonar.sources=…
  sonar.tests=…
  sonar.test.inclusions=…
  sonar.javascript.lcov.reportPaths=…

I also have it being run in GH actions:

• name: SonarQube Scan
  uses: SonarSource/sonarqube-scan-action@v5 # Ex: v4.1.0, See the latest version at Official SonarQube Scan · Actions · GitHub Marketplace · GitHub
  env:
  SONAR_TOKEN: ${{ secrets.SONAR_TOKEN }}
  SONAR_HOST_URL: ${{ var.SONAR_HOST_URL }}

Is it an issue with my sonarproperties? :-/

The odd part related to this is the other repos in the organization get the PR post, it’s just one repo that’s not..

I do also have this enabled in the DevOps Platform Integration tab.

Enable analysis summary under the GitHub Conversation tab

When enabled, a summary is displayed under the GitHub Conversation tab. Notifications may be sent by GitHub depending on your settings.

[ganncamp (G Ann Campbell)]

Hi,

Welcome to the community!

To be clear, when you say “post on the PR” you’re talking about PR decoration in GitHub?

If so, the answer is probably entirely unrelated to your analysis parameters.

I would start in your server logs. Specifically, start by checking your ce.log (compute engine log) for errors at the end of server-side processing of a PR from the project. If that’s clean, then the next step is to double-check the project binding.

 
HTH,
Ann

[dswanson (Dan Swanson)]

Thank you for replying! I am referring to the PR decoration in GitHub! (I think.. I’m referring to the comment that the sonarqube app makes on PRs.

I did check my ce.log yesterday and did find an issue with not having the content:read permission and fixed that which fixed other issues where the status wasn’t posting on the PR. So that did work! But I’m wondering if I can get the comment to post.

I did also check the project binding, and that’s all good.

[ganncamp (G Ann Campbell)]

Hi,

@dswanson

which fixed other issues where the status wasn’t posting on the PR. So that did work! But I’m wondering if I can get the comment to post.

Uhm… huh?

Is it fixed (comment posting) or … not?

 

Ann

[dswanson (Dan Swanson)]

It’s now posting a status check* which at least lets us know that the sonarqube scan failed the quality gate. It’s still not making a comment post.

[ganncamp (G Ann Campbell)]

Hi,

I think words are getting in the way here. Could you give me screenshots, redacted as necessary, of what is and what is not working as expected?

 
Thx,
Ann

[dswanson (Dan Swanson)]

Makes sense!

Here’s a repo that’s working in the same org:
It posts both the status check and PR comment.

The repo that’s not working only posts the status check:

[ganncamp (G Ann Campbell)]

Hi,

Thanks for the screenshots!

Okay, so PR decoration is what’s not happening.

Based on this:

@dswanson

I did check my ce.log yesterday and did find an issue … and fixed that

You don’t see any errors in your ce.log related to this project’s decoration. (Right?)

So that leads me to think it’s about the configuration. Is the project bound?

 
Ann