[codex] Upload build env vars during init#2306
Conversation
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (7)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub. |
|
Merging this PR will not alter performance
Comparing 
Footnotes
|
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
Following review of PR #2306, the build onboarding wizard now defers GitHub Actions / GitLab CI secret upload until AFTER a build has been successfully queued — rather than before. This prevents users from ending up with orphan secrets in a repo whose build was never proven to work. New ordering on both iOS and Android tracks: save credentials → ask-build ├─ user skips build → exit (no secrets pushed) ├─ build request OK → detecting-ci-secrets (if entries) → … → exit └─ build request err → exit (no secrets pushed) All ci-secrets-* state transitions that previously fell back to ask-build on skip / failure now route to build-complete instead, because by the time those paths fire the build has already been dispatched. bun.lock: workspace version bump from 7.104.0 → 7.108.2, picked up mechanically by bun install (was stale on main).
1 participant
Summary (AI generated)
ghand GitLab CI/CD variable upload throughglab.Motivation (AI generated)
Users who finish
build inithave local signing credentials, but still need the same env vars in their git hosting CI/CD provider to run cloud builds from pipelines. This adds an assisted path directly at the end of onboarding while preserving explicit confirmation before overwriting existing remote values.Business Impact (AI generated)
This reduces setup friction for native cloud builds, especially for users configuring GitHub Actions or GitLab CI. Easier CI setup should improve activation for Capgo native builds and reduce support around manually copying large signing env vars.
Test Plan (AI generated)
bun run cli:checkbun run cli:build && vue-tsc --noEmitGenerated with AI