Ello,
I am using SonarCloud for a project I have hosted on GitHub.
I have recently changed the name of my GitHub account, and due to the project not being hosted under an organization I became concerned of anything breaking.
I know that GitHub themselves redirects all links to repositories, but didn’t consider SonarCloud’s process until after. And on reading some other posts regarding like issue, believed it may be of concern.
At the moment SonarCloud seems to still be operational under previous links, however I am not sure how long that could last. When I was poking around with the badge links, I noticed that SonarCloud is still operating under the previous URL and does not identify any project under the new repo URL.
I wanted to make this post to check if there would be any justified concern on my part, and if there is any action I need to take to remedy this situation.
I have noticed that some apps on this change have ceased functioning (have been migrated to the new URL), and some have not (are still using the old URL). Which is a can of worms on itself.
Any response on the matter would be greatly appreciated.
Thank you for your time.
I changed my GitHub username. Eg remotes at https://github.com/username/repo now follow my new username. I know GitHub starts redirections from the old repo URLs to the new one (GitHub.com/old/repo now redirecting to GitHub.com/new/repo), so long as no new project overrides it. SonarCloud seems to still be operating under the old URLs, and I’m not sure if this is something to be concerned over.
I believe I saw some other posts on the forums under similar topics, that had intervention from SonarCloud staff, and thought I’d throw the question.
Some apps I use on my projects migrated to the new URL in their respective platform (and broke some links in the process). But some (SonarCloud included) still seem to be pulling data from the old URL.
Thanks for sharing further details and explaining the situation.
When you change your username on Github, GitHub automatically creates redirects for repositories. On the SonarCloud side, all your repositories are still mapped to your old URL, which is fine given the redirects Github provides. You should still be able to use SonarCloud as usual to analyse your imported projects even with the old URL and not actions are needed on your side.
Could you please confirm that so far everything is still working as usual on the SonarCloud side?
Hi,
Thanks for the reply, sorry I didn’t see it sooner.
So far everything has been working fine…
But a concern of mine (despite it being unlikely) would be that someone would be able to override my previous repository URL (now that it is freed) as GitHub takes priority for active repositories over redirects.
This may be a really mute point, but it is somewhat of a concern for me as it could be an attack vector of sorts.
I understand your concern. If you really want to avoid this risk, you could simply delete your projects and reimport them on SonarCloud. Then, on the SonarCloud side, they will be bound to the updated URL.
Just note that you would lose your SonarCloud history on those projects if you do it.
Well,
Digging through settings I found an easier solution, that honestly should be better documented.
In the administrative binding sections if you click on the currently bound repo and then hit save, the repo URL gets updated.
Nowhere is this explained, but I guess if it works it works…
