fix: use direct Cloudflare secrets for deploy workflows#42
Conversation
Cloudflare WAF blocks GitHub Actions IPs from reaching ChittyConnect, making OIDC-based credential fetch impossible. Switch to direct CLOUDFLARE_API_TOKEN and CLOUDFLARE_ACCOUNT_ID secrets. Also simplifies deploy-pages.yml by removing the get-credentials job and using secrets directly. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
Warning Rate limit exceeded
⌛ 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 (2)
✨ Finishing Touches🧪 Generate unit tests (beta)
📝 Coding Plan
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
id-token: writepermission (no longer needed)get-credentialsjob entirelyContext
Cloudflare WAF blocks GitHub Actions IPs from reaching
connect.chitty.cc, making the OIDC zero-secret approach non-functional. Direct secrets match the pattern used by chittyconnect's own deploy workflow.Required setup
After merging, set these repo secrets:
CLOUDFLARE_API_TOKEN— Cloudflare API token with Workers deploy permissionsCLOUDFLARE_ACCOUNT_ID— Cloudflare account IDDepends on
🤖 Generated with Claude Code