Welcome to Codecov! No, you aren’t doing something wrong, due to the way that GitHub exposes org renames, they are tricky to handle by third parties such as Codecov.
Can you uploaded coverage since the rename? Are you using the Codecov app on GitHub, and if so, have you confirmed it’s still allowed in third-part restrictions?
I think I have the same problem. I had to rename an org I was trying to use codecov on, and after the switch I get 404s in the settings panel, and I can’t push coverage reports anymore. It also doesn’t list the org’s repositories anymore when I go to codecov settings urls with the old org name.
Hey Paul: can you check your 3rd party installed apps?
And try reinstalling Codecov there? If that doesn’t work, we can try a manual rename on our side (we do rely on the Github org name as the central connection point in DB, e.g., no unique orgid coming from Github).
I have the same problem after transferring a repo across organizations and renaming it.
Codecov is installed in the github org and has access to the repo
Hi codecov support team, I have same problem and re-installing doesn’t fix my case.
After uninstalling GitHub App (GitHub Apps - Codecov · GitHub), it’s stuck showing “Syncing GitHub Teams” at Codecov . The old org name doesn’t disappear and new one never appear even if installing the GitHub App again and again.