SonarCloud Not Syncing GitHub Repositories – Showing Incorrect Placeholder Repos Instead

Hey y’all, I’m experiencing a strange issue with SonarCloud not detecting or syncing with my GitHub repositories. Everything is configured correctly, but when I try to create a new project, my repositories aren’t showing up. Instead, it seems to be displaying some placeholder repositories like common, account-service, api-gateway, etc.

Here’s a screenshot for your reference: Upload and share screenshots and images - print screen online | Snipboard.io

Any help would be greatly appreciated! Thanks!

Hey @martijn.cachet

Thanks for reporting this. I don’t experience this on my end, and I can’t find anywhere in the code where we have some “placeholder” like these.

Could you go ahead and create the project and then see what repo it is bound to?

I find it very unlikely that there is a security issue here, but I really don’t like the idea of you being able to see projects you don’t recognize. So just for a moment, I’m unlisting this thread. :slight_smile:

Hey Colin, thanks for your quick reply! Interestingly, it’s linked to a different organization, but I have a feeling I know why that’s happening. Previously, our organization on GitHub was called ‘dev-kitchen’, but we rebranded to ‘cachet-studio’.

When I link the ‘common’ repository, it points to GitHub - dev-kitchen/common, which belongs to the ‘dev-kitchen’ organization — an entity that we do not own. That explains the mismatch.

Do you think this could be some kind of caching issue? My organization settings in SonarCloud appear to be correct (screenshot: Upload and share screenshots and images - print screen online | Snipboard.io).

Again, thank you for looking into this!

Hm. Weird, and I’ll be reporting that. Luckily those are open source repos…

I would suggest that you click down to “organization binding” – do you see that your org is bound?

Yep, it’s bound to the correct organisation, as you can see in the screenshot.

But after clicking ‘Update path’, it seems to be working again—I can now see the repositories I would expect. Some kind of bug, but glad to have it working again. Thanks for your time, and if you need anything else, feel free to let me know!

2 Likes

Ah, there we go! You’re back in action.

From our devs:

We were relying on GitHub redirects, but seems like this organization namespace was claimed by someone else
If it were private repos, they wouldn’t be listed because the app has no permission to see them
But very strange behaviour nonetheless

1 Like