Hi Jacek,
I believe I have found the reason why it hasn’t been working and it is because we use a headless user account and generate the PAT from it. Until recently this user has had code r/w access. However, to make projects compliant we have started restructuring the permissions on projects so only users who needed to change code are only allowed to do so. This headless account was left out of the user group that had the write permission on the repositories and therefore SonarCloud it appears SonarCloud wasn’t allowed to interact with the PR Status Check. So the issue is totally on our side.
As for the binding, we haven’t bound any projects yet as we haven’t understood the significance of this action. What does binding a Sonar Cloud project have?
Many thanks,
Bob.