We have an orphaned GitHub repository binding left behind by a project that
was deleted. It is now preventing us from binding our active project to
the GitHub repository.
OLD project (deleted, inaccessible):Connect-Assistance_helios_api
→ This is the one with the orphaned binding. Please remove its binding
(or whatever residual record is still linking it to the repo).
→ Visiting SonarQube Cloud
returns: “The requested project does not exist, or you have not been
granted access.” It also no longer appears in our organization’s project
list. I’m an admin in both the SonarQube Cloud org and the GitHub org.
NEW project (active, working — DO NOT delete or modify):connect-assistance_helios-api
→ This is our current, healthy project. Analyses run correctly, Quality
Gate works, PRs are analyzed. We just need it bound to the GitHub repo
so PR decoration works.
What is broken
On the “Repository binding” page of the NEW project
(connect-assistance_helios-api), the GitHub repo Connect-Assistance/helios_api
shows up as “Already bound”, and the Save button is disabled. The repo is
still considered bound to the OLD (deleted) project.
As a result, PR decoration (inline comments / annotations on pull requests)
does not work, even though analysis itself is fine.
What I need
Please remove the orphaned binding associated with the deleted project Connect-Assistance_helios_api so that I can bind Connect-Assistance/helios_api
to the active project connect-assistance_helios-api.
To be explicit: please do NOT delete or change the active project connect-assistance_helios-api. Only the residual binding from the deleted
old project needs to be cleaned up.
Just so I understand correctly: You removed the old project in SonarQube, and then you created the new one, but now you’re not able to bind the new one to the same repository, correct?
Was the deleted project in the same SonarQube organization as the new one?
Thanks!
The old project was removed/deleted and is no longer accessible. It also does not appear in our SonarQube Cloud organization project list anymore.
After that, I created a new active project and configured analysis successfully. The new project is working correctly: analyses run, the Quality Gate works, and PRs are analyzed.
The issue is that I cannot bind the new project to the same GitHub repository because SonarQube Cloud still shows the repository as “Already bound”, apparently due to the old deleted/inaccessible project.
And yes, the deleted old project was in the same SonarQube Cloud organization as the new one:
Organization: connect-assistance
Old deleted/inaccessible project:
Connect-Assistance_helios_api
New active project:
connect-assistance_helios-api
GitHub repository:
Connect-Assistance/helios_api
So the problem seems to be that the GitHub repository binding was not fully removed when the old project was deleted.
Did you by any chance delete and re-create the organization (connect-assistance) at any point? (I guess not but I’d rather ask)
Did you remove and recreated the organization binding, meaning, did you uninstall the SonarQube Cloud GitHub app from the GitHub organization before reinstalling it again?
No, we did not delete and re-create the SonarQube Cloud organization connect-assistance.
Regarding the GitHub organization binding, I don’t believe we uninstalled and reinstalled the SonarQube Cloud GitHub app either, but I can double-check internally if needed.
One additional important detail: the broken/inaccessible project still appears to be consuming analyzed lines in our SonarQube Cloud organization.
In the project list, I can see two helios_api entries with very similar names/keys. One is the active project we can access and use, and the other one is the broken/ghost project. When I try to open the broken one, SonarQube Cloud shows:
“The requested project does not exist, or you have not been granted access.”
So this project is not only blocking the GitHub repository binding, but it also seems to still count toward our analyzed Lines of Code usage, which affects billing/plan limits.
What we need is for SonarSource to remove/delete/clean up that ghost/inaccessible project and its residual GitHub repository binding. The active project should not be deleted or modified.
I can confirm I found Connect-Assistance_helios_api as part of the Connect Road Assistance organization.
Do you remember when approximatively you deleted this project?
That’d be helpful to try and find the root cause of the issue (the project not being actually removed from the database).
In the meantime, I’ll try to see what I can do to unblock you.
Yes, that’s correct, and both projects are within the same SonarQube Cloud organization (connect-assistance).
One clarification though: I did not intentionally delete the old project myself. For some reason, it ended up in an inconsistent/broken state inside SonarQube Cloud. If I try to access it, SonarQube says the project does not exist or that I do not have access to it, and it no longer appears in the organization project list.
Because of that situation, I created a new project (connect-assistance_helios-api) so we could continue running analyses. The new project is working correctly, but I still cannot bind it to the GitHub repository because the old “ghost” project still appears to own the repository binding.
Additionally, that orphaned project also seems to still be consuming lines from our paid subscription, even though it is inaccessible/non-functional.
So at this point, I believe there is some residual/orphaned state left behind in SonarQube Cloud associated with the old project (Connect-Assistance_helios_api) that needs to be cleaned up manually.
Yes, I am an admin of the SonarQube Cloud organization connect-assistance. About the “ghost” project: when I try to open it directly, SonarQube returns “The requested project does not exist, or you have not been granted access”. However, it still shows up in our organization’s lines-of-code metrics, and — most importantly — it is what is blocking the binding. When I try to bind the new project connect-assistance_helios-api to the GitHub repo Connect-Assistance/helios_api, the repo is shown as “Already bound” (bound to the deleted ghost project), and the Save button is disabled.
Yes, we use GitHub to log in to SonarQube Cloud.
No, we do not use automatic GitHub provisioning. We are on the Team plan and our Members page shows the banner “You can also automatically synchronize members with your GitHub organization” with a Configure button (i.e. not yet configured). Members are added/managed manually, so we are effectively on JIT.
Yes, I have full access to the GitHub repository Connect-Assistance/helios_api. The repo is active and I am also an admin in the GitHub organization.
Let me know if you need anything else from my side to clean up the orphaned binding so we can re-bind the active project.
I was able to delete the orphan project with key Connect-Assistance_helios_api. I confirm that the project with key connect-assistance_helios-api is still intact.
You should hopefully be able to bind your GitHub repo to the remaining project now. Let us know if you have any issues.