Automate notices testing#477
Conversation
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ 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: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (5)
✨ 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 |
|
@coderabbitai full review |
✅ Actions performedFull review triggered. |
Adding GitHub Actions automation to reduce manual steps in the in-product notices testing workflow.
Spec doc: https://mattermost.atlassian.net/wiki/spaces/Security/pages/4550393860/Automation+-+In-Product+Notices+Testing
notices.jsonchanges. It performs three checks:notices.schema.jsonHEAD-requests every action_param,image, and inline URL and fails if any are unreachableauto-test-pr.yml — runs when a PR is opened or reopened against the release branch. It automatically creates a mirror PR targeting master with a [Test] prefix on the title, a link back to the original release PR, and the pre-filled /cloud command to configure a test server after merging.
Supporting files: