My organisation uses Sonarcloud across several projects in github, and has the sonarcloud app installed. Most are projects have sonarcloud functioning correctly, but one project is broken.
In this project, Sonarcloud is not identifying Pull requests, instead marking everything as branches, even though develop is correctly identified as the main branch (and PRs are made to develop).
Therefore the Sonarcloud bot is not commenting on PRs (ie. no pull request decoration).
Unfortunately the documentation offers no clue as to a solution, as it presumes pull request analysis works automatically for Github.
Thanks. I will try that, however all our projects use identical pytest.ini, github actions .yml and sonar-project.properties files, and yet only one project is having sonarcloud problems
Therefore the suggested trigger is not present in projects that do run sonarcloud correctly so I don’t understand why it would be the root cause of the issue preventing bot comments and PRs?
One unique sonarcloud warning that impacts the project without proper functionality is
The following error(s) occurred while trying to import coverage report:
Invalid directory path in 'source' element: {repo_name}
where {repo_name} is the name of the project and the top-level folder
We will need to escalate. Further projects in our repo are developing sonarcloud errors despite our making no changes in github actions or sonarcloud.properties in those projects.
These errors are slightly different by project and look like github and sonarcloud failing to integrate correctly. Can we discuss this live with Sonarcloud support?