-
Notifications
You must be signed in to change notification settings - Fork 4
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
codecov #171
Comments
No I don't have admin access. @bart-v could you have a look? |
Beside possible reactivation, maybe we also need a token. It can be an organization wide secret (this way we won't need to ask again for emodnet.wcs) https://ropensci.org/blog/2024/05/24/ropensci-news-may-2024/#token-now-needed-for-code-coverage-via-codecov-and-covr-on-github-actions |
Now the badge is working but having the token might still be a good idea (I fear we might run into rate limits otherwise? Or maybe there is already an organization-side secret?) |
There was already an organization-side secret. |
Ok, thanks, sorry. Following https://github.com/EMODnet/emodnet.wfs/actions/runs/10353537203 now |
ah indeed "Not valid tokenless upload", the new token needs to be stored as new organization-wide secret. So sorry!! |
OK done, try now? |
Weirdly I got the same error again https://github.com/EMODnet/emodnet.wfs/actions/runs/10353537203/job/28690809753#step:6:46 🤔 (I can't explore more today, sorry) |
Seems a bug in codecov |
OK, I now used the correct token, i.e. like here |
thanks!! |
@salvafern do you have admin access to https://app.codecov.io/gh/EMODnet? I think the repo might need to be reactivated now that I renamed it.
The text was updated successfully, but these errors were encountered: