fix: use env var to check VT_API_KEY instead of secrets in if condition#18
Merged
fix: use env var to check VT_API_KEY instead of secrets in if condition#18
Conversation
GitHub Actions does not allow referencing secrets in step-level `if` conditions. The workflow parser rejects the entire file, causing all release builds to fail with "workflow file issue".
Contributor
Build Artifacts
Built from 843a7cb. Artifacts expire after 90 days. |
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.
Summary
if: secrets.VT_API_KEY != ''secretscontext inifconditions, causing the workflow parser to reject the entire fileHAS_VT_KEY=trueenv var, then checkif: env.HAS_VT_KEY == 'true'Test plan
gh workflow run release.yml