deploy: always sign with PRIVATE_KEY (never PRIVATE_KEY_DEV)#8
Conversation
|
Warning Review limit reached
More reviews will be available in 28 minutes and 4 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, 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 include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ 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 |
|
Reviewed bf005cf: APPROVE — deploy workflow always signs with secrets.PRIVATE_KEY (drops the PRIVATE_KEY_DEV fallback). One-line key change; checks green. |
Per project policy, deploy workflows must always sign with
secrets.PRIVATE_KEY. Replaces thegithub.ref == 'refs/heads/main' && secrets.PRIVATE_KEY || secrets.PRIVATE_KEY_DEVconditional in: rainix.yaml