Conversation
) The build-arg step composes a full URL from a bare repo slug: DATA_REPOSITORY=https://github.com/${owner}/${secrets.DATA_REPOSITORY} so `secrets.DATA_REPOSITORY` is a slug (e.g. `awesome-time-tracking-data`), not a URL — by repo convention shared with docker-build-publish-*.yml. PR #970 added bulk runtime-env forwarding but passed the slug through unchanged, so the pod env saw `DATA_REPOSITORY=awesome-time-tracking-data` and the app rejected it ('DATA_REPOSITORY' is not defined. Content features will be limited.). Mirror the same slug → URL transformation in the runtime-env step: if the secret doesn't already look like a URL (http(s):// or git@), prepend `https://github.com/${repo_owner_lc}/`. The cluster Secret now matches what the build-arg already produces. Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Free Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Note 🎁 Summarized by CodeRabbit FreeThe PR author is not assigned a seat. To perform a comprehensive line-by-line review, please assign a seat to the pull request author through the subscription management page by visiting https://app.coderabbit.ai/login. Comment |
1 participant
Cascade of PR #974 — DATA_REPOSITORY now gets the slug→URL transformation at runtime forwarding, matching the build-arg.