Passing secrets.CODECOV_TOKEN not recognized
See original GitHub issueHaving set up the secret CODECOV_TOKEN
and passing it as ${{ secrets.CODECOV_TOKEN }}
the upload fails with the message:
HTTP 400
Please provide the repository token to upload reports via `-t :repository-token`
This is both for v1
and v1.0.5
of codecov-action
.
It seems that the action’s environment variable CODECOV_TOKEN
is not set properly or not recognized?
It should be mentioned that this has recently started failing, without changing the actions workflow otherwise, i.e., it used to work, but now throws this error.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:2
- Comments:7 (3 by maintainers)
Top Results From Across the Web
Github Checks do not Show Up - Support - Codecov
Github Checks are not showing up on my pull requests (I'd expect both patch and project checks) · I see Unable to find...
Read more >Security - Codecov
Scanning repos for secrets (API keys, passwords, etc) to ensure they are not stored or hard coded in our code base. Usage of...
Read more >code coverage - Why is codedov not showing the report?
Run codecov/codecov-action@v2.1.0 ==> linux OS detected ... [2022-01-10T09:50:48.495Z] ['verbose'] Passed token was 36 characters long ...
Read more >Setting up a CI/CD workflow on GitHub Actions for a React ...
You will see a token, that token will not be useful if your ... you must include the codecov token, through a secret...
Read more >airflow-codecov-action - Git at Google
Note: This assumes that you've set your Codecov token inside Settings > Secrets as CODECOV_TOKEN . If not, you can get an upload...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hi @CasperWA, thanks for bringing this up! You’re right, secrets are not available for forks of repositories, therefore the token wasn’t available when you tried to upload to Codecov from the forked repository. I’ll push an update to our readme soon because it’s definitely worth clarifying
With regards to tokenless uploads, we do plan to support them when GitHub releases an API for Actions around early 2020.
@thomasrockhu Oh thanks! Reading about the issue earlier in other discussions, switching to the latest version didn’t seem to help them. But apparently I should have tried it out, because it works!