-
Notifications
You must be signed in to change notification settings - Fork 213
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error message "Token required because repository is private" #1602
Comments
We have the same issue |
@ruokun-niu can you try on v5? @BAStos525 can you post the Codecov output or link to CI? |
first time trying codecov, getting this issue consistently on my public repo with v5.0.7
it additionally seems strange that it continues after it has already failed, which to me indicates a low quality implementation, and since I need confidence in my code quality tools, I now have no desire to use Codecov |
@mbrock can you send me a link to CI for this? |
@ruokun-niu @BAStos525 gentle bumps |
Hey @thomasrockhu-codecov , sorry for the late update. Somehow I did not receive the notification at first. I'll give this a try today or tomorrow |
Hi @thomasrockhu-codecov , I attempted to use codecov/codecov-action@v5, but the workflow failed with the following error
Link to workflow: https://github.com/drasi-project/drasi-core/actions/runs/12188485129/job/34001570398 This is a branch in a public repository |
@ruokun-niu got it, taking a look! |
@ruokun-niu do you mind running this in verbose mode? |
@thomasrockhu-codecov here is the log from verbose mode |
@ruokun-niu thank you, do you mind re-running again? We made a fix on our side |
Hi Codecov,
I am trying to use the Codecov github actions in my public repo (https://github.com/drasi-project/drasi-core). Specifically, I am testing by creating a PR from a forked branch. However, I ran into the following error
My repository was once private when we set codecov up, and we have changed the visibility to public couple weeks ago. Any idea why this is happening?
The text was updated successfully, but these errors were encountered: