Hi All,
We have an enterprise plan and our Sonarqube Cloud org is bound to our Github Org. Our CI manually creates our projects (and project keys) if they don’t already exist which in sonar are unbound projects (there is no repo binding under project → administration → general settings → repository binding). We do not create projects from repositories in the UI, rather what we do would be similar to using the “create a project manually” from the UI’s “Analyze new project” selection.
What we are seeing is after our sonarscanner steps run in our actions CI on PR, after the build and sonar steps in our CI execute and complete we are getting PR decorations!
Now we spent a good deal of time creating additional steps in our CI to create the repo bindings and handle mono repo binding (by sniffing out the api calls in the network xrf fetch info) but it appears we don’t need to actually bind the repos to projects?
I’d like some clarification if this is expected behavior by virtue of us being bound at the org level and unbound projects don’t matter if the ci is executed from the repo ci actions in question? Just trying to understand what we are experiencing, based on all the documentation repo bindings are required for PR decorations to work but in our case its working without.