fix(portal-deploy): load expose refs only on their branch - #334
Conversation
Ordinary HTTP preview was paying the cost of x402, safety, game, and CLI docs before the recipe ran. Keep those reads on the matching branch and treat service ready at as the HTTP ready signal.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 2 included reviews per hour; 0 remain after this review. 📜 Recent review details🔇 Additional comments (1)
📝 WalkthroughSummary by CodeRabbit
WalkthroughChangesPortal expose guidance
Merge Risk: ⚪ Minimal · up to This localized change adjusts when reference documentation is opened and clarifies readiness and handoff instructions; no actionable merge-blocking risk remains beyond normal checks and review. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Full details: Linked Issues checkExplanation The changes address issue [ 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. (1 skipped: 1 unsupported.) ✨ Finishing Touches✨ Simplify code
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 |
Summary
Ordinary HTTP preview was loading x402, safety, game-hosting, and CLI reference docs before the expose recipe ran. Agents now follow the workflow in order and open those files only on the matching branch. HTTP ready is the
service ready at https://...line, not the first relayhttps://. Portal friction, if any, is one sanitized sentence in the conversation — no finding store, feedback CLI, or extra GitHub/relay queries.Closes #332
See also: #326, #331