fix(ci): guard EAS jobs via env, not a job-level secret if#110
Merged
Conversation
GitHub Actions forbids the `secrets` context in a job-level `if:`, so the guard added in the previous CI-health change caused a workflow startup_failure (the EAS Build/Update/Submit workflows showed red at the file level). Mirror `secrets.EXPO_TOKEN` into a job-level `env` and guard each step with `if: env.EXPO_TOKEN != ''` instead — the jobs are a clean no-op (green) when the token is unset and run normally once it's configured. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
Follow-up to #109. GitHub Actions forbids the
secretscontext in a job-levelif:, so the guard I added there made the EAS workflows fail at startup (red at the workflow-file level).Fix: mirror
secrets.EXPO_TOKENinto a job-levelenv, then guard each step withif: ${{ env.EXPO_TOKEN != '' }}. The EAS jobs are now a clean no-op (green) when no token is configured, and run normally once you addEXPO_TOKEN.(The integration guard from #109 — step-output presence check — already works; Integration Tests went green on main.)
🤖 Generated with Claude Code