fix(ci): skip the relay deploy when the fork has no relay to deploy to - #42
Conversation
This fork owns none of the upstream production infrastructure, so the deploy and the release chain that reads its state have nothing to talk to. Keeping the workflows in place lets them start working the moment the environment carries credentials. Signed-off-by: Yordis Prieto <yordis.prieto@gmail.com>
PR SummaryLow Risk Overview In Reviewed by Cursor Bugbot for commit 06c8ba7. Bugbot is set up for automated code reviews on this repo. Configure here. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Team Run ID: 📒 Files selected for processing (2)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. WalkthroughThe workflows now check production relay credentials before running relay operations. Release jobs also require a non-empty relay URL before building, publishing, deploying, or announcing releases. ChangesRelay credential gating
Estimated code review effort: 3 (Moderate) | ~20 minutes Merge Risk: ⚪ Minimal · up to Relay deployment and relay-dependent release work now skip cleanly when production relay credentials are unavailable, while continuing to run when configuration is present. No current merge-blocking risk is identified. Suggested reviewers: Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
Full details: Description checkExplanation The description explains the problem, the change, and the intended behavior, but it omits the required "What Changed," "Why," and "Checklist" sections. It also does not identify UI changes as not applicable. Full details: Docstring CoverageExplanation No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (2 skipped: 2 unsupported.)
✨ 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 |
Thread transfer impact✅ Thread transfer remains within every enforced ceiling.
Baseline: Scenario and decoded snapshot size10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.
Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed. |
productionenvironment carries no variables or secrets, so the relay deploy fails at its first credential lookup.