Hi, We’re currently migrating our GitHub repositories from one organization to another and want to continue supporting SonarQube scanning for the migrated repositories.
Our goal is to use the existing SonarQube organization for the migrated repositories. As I understand it, this would require unbinding and then rebinding the SonarQube organization to the new GitHub organization. Could you please confirm if the following process is correct?
Uninstall the SonarQube app from the existing GitHub organization to enable rebinding.
Install the SonarQube app in the new (migrated) GitHub organization.
Bind the existing SonarQube organization to the new GitHub organization.
Refresh the project bindings.
Also, would rebinding and refreshing the project bindings affect the total lines of code analyzed (and therefore the billing), or would the cost remain the same as before?
Your understanding of the steps is correct, and they’re also detailed in the official documentation.
Be sure to initiate your new app install from the global Administration > Organization Binding section. This is important because installing the SonarQube Cloud app directly from the GitHub marketplace doesn’t create the actual binding within SonarCloud.
Regarding your question: Rebinding or refreshing project bindings will not impact the total lines of code analyzed or the billing. Your costs will remain unchanged.
Thanks, Colin, for clarifying this I really appreciate you getting back to me.
One more thing regarding user management, we currently have automatic sync with GitHub enabled for members. I’m just wondering about the access part if I delete the existing GitHub app, will it affect my user permissions? I’ll need admin access to set up the binding with the new organization.
To be safe, go ahead turn off member sync before unbinding the organization. I’ll verify with the team whether this step is essential, but until that’s clarified I would suggest you take this precaution.
To follow up on the previous points and address your concern regarding access:
When you unbind the GitHub app, SonarCloud does not automatically change or revoke existing permissions. You won’t find yourself locked out of the organization during the transition.
As long as you have Administrative privileges on the new GitHub organization, you will be able to complete the rebinding process and manage the SonarCloud organization without issue.