ci: provide API_BASE_URL so env generation no longer fails - #23
Conversation
The Lint/Test/Build job ran generate-env.mjs (via pretest:ci and prebuild), which hard-fails when API_BASE_URL is unset. Inject it at the job level (secret/var override, committed public fallback) and pass the same build-args to the deploy image build. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Code Review Could Not Complete
|
| Options | Enabled |
|---|---|
| Bug | ✅ |
| Performance | ✅ |
| Security | ✅ |
| Business Logic | ✅ |
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe CI workflow adds API and Goong configuration variables to the CI environment and passes them as build arguments when creating the deployment Docker image. ChangesCI environment propagation
Estimated code review effort: 1 (Trivial) | ~5 minutes Suggested reviewers: Poem
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
The Lint/Test/Build job ran generate-env.mjs (via pretest:ci and prebuild), which hard-fails when API_BASE_URL is unset. Inject it at the job level (secret/var override, committed public fallback) and pass the same build-args to the deploy image build.
Summary by CodeRabbit