Repository navigation
ci(cloudflare): fail a pull request whose vertical has no stage edge placement - #1035
Conversation
Changed Files
|
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 35 minutes. View limit detailsLimit details: You’ve used the included review currently available. Review configuration: ⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Advanced Run ID: 📒 Files selected for processing (4)
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 |
Why the change
A vertical merged without its Cloudflare placement (as #889 Inventory did) only failed the stage edge deploy after merge, so this moves the check onto every pull request.
Special things to note
Repository Tooling Testsjob and needs no secrets, so fork PRs get it too. The secret-gatedCheck the Cloudflare edge deploy configurationjob is unchanged.createModernConfigdefaults every vertical toCLOUDFLARE_WORKER_CPU_MS.vertical, so the docs checklist covers picking it instead of a check.stage-edge-units.mtsso both use one list.Change outline