I have a similar situation as in this (now closed) support request:
Specifically, I have a repo that originally was private but now is public:
The codecov for it is 100% but the badge is showing “unknown” and under codecov settings it is showing the message “Repository is activated and using one private repo credit.”
So clearly codecov still thinks my repo is private even though it has been public for days.
I tried removing it from codecov and adding it but it seems it was not really “removed” but rather “archived” so the restored version still has the same issue.
I suspect that only codecov can fix this but if anyone has a work around I’d appreciate it!
Thanks for the status update. I would guess that the pattern of starting with a private repo for initial development and then making it public when it is ready is fairly common, so if there are any “best practices” we should use to avoid this issue in the future please let us know! Thanks!
Other than this small issue, codecov is fantastic!
Ok updated! I haven’t seen this issue before but my guess is that the “private” setting was just cached incorrectly in our DB. If we see it popping up again will look for a more foundational solution.
I have the same issue with my repo: Codecov
The related bitbucket repository is public (Bitbucket), but I have no options to change the codecov repo to be public.
Any help would be appreciated!
Hi @jerrod, yes I did rename the repo – but I’ve deleted that one now and the one you link is different.
I was setting up a test repo for a workshop later that evening. I changed from private to public half-way through testing, and that seemed to break codecov. I later deleted that repo, and during the workshop made a different one (the one you’ve linked). That one is okay (was always public). I should have updated here after deleting the test repo – nothing for you to do! But I do think the fix should be integrated upstream. Thanks!
Hi, @jerrod, I also did as JeffFessler in the same workflow, and can’t be read publicly. I think making a recache or pub/private trigger in general is better, because I found there tripple times, and thought It’s my fault that I missed somthing.
Hi everyone, thanks for reaching out here. Looks like it’s a bug on our end.
I’ll pull the list of repositories that we need to switch over from this thread and post back here. Please reply if we have missed yours. We are also following up with the product team to get this fixed.