ci: expose CODECOV_TOKEN via env so the step if is valid - #419
Merged
Merged
Conversation
The coverage workflow failed on every trigger because the secrets context is not allowed in a step-level if (schema error, 0 s runs). Map it to a workflow env var and check that instead; without a token the upload step is skipped and the job stays green.
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.
The coverage workflow from #418 failed on every trigger because the
secretscontext is not allowed in a step-levelif(schema error, 0 s runs on main).Map the secret to a workflow-level
envvar and check that instead; without a token the upload step is skipped and the job stays green until the Codecov app is connected.Closes #417