We recently migrated all our repositories from Bitbucket Cloud to GitHub (same organization, same code, same default branches). Our SonarCloud projects were originally created with a Bitbucket binding (ALM integration), and we’d like to keep their full analysis history, issues, and measures.
Our question: Is it possible to switch the ALM binding of existing SonarCloud projects from Bitbucket to GitHub without losing the project history?
Specifically:
Can we re-bind an existing project to the corresponding GitHub repository in place, or does this require deleting and re-creating the project (which would lose history and require a new project key)?
If re-binding in place is supported — what’s the recommended procedure (project key, PR decoration, branch analysis)?
Do we need to set up a new GitHub-based SonarCloud organization, or can the existing organization be re-connected to the GitHub App?
Any impact on sonar-project keys / CI configuration (we use GitHub Actions for analysis now)?
Context:
Existing org bound to Bitbucket Cloud
All repos now live on GitHub under org troii
CI moved to GitHub Actions
Thanks for your help!