ci: disable Codecov uploads until a token is configured - #76
Merged
Conversation
Both upload steps fail on every run with "Token required because branch is protected" — CODECOV_TOKEN is not set as a repository secret. The failures are non-fatal (fail_ci_if_error: false), so nothing was gated on them, but it means the Codecov data has been silently stale while every job log carried the error. Gate both steps behind `false` rather than deleting them, so re-enabling is just removing that guard once the secret exists. The pytest invocation still writes coverage.xml and junit.xml, so nothing else has to change. The README Codecov badge is left in place; it will show whatever the last successful upload reported until the token is added.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Both Codecov steps fail on every CI run:
CODECOV_TOKENis not set as a repository secret. Because both steps usefail_ci_if_error: false, nothing was ever gated on them — but the uploads havebeen silently failing, so the Codecov data is stale, and every job log carries
the error.
Disabled rather than removed, as requested: both steps stay in the workflow,
gated behind
false. Re-enabling is adding the secret and dropping the twoguards.
python -m pytest --cov-report=xml --junitxml=junit.xmlis unchanged, so theartifacts are still produced and ready the moment the uploads are switched back
on.
The README Codecov badge is left in place — it will keep showing whatever the
last successful upload reported until the token is added. Say the word if you'd
rather it came out too.
🤖 Generated with Claude Code