TEMP: scratch workflow for investigate-prompt iteration - #662
TEMP: scratch workflow for investigate-prompt iteration #662JakeSCahill wants to merge 3 commits into
Conversation
…re prompt Deliberately breaks a real selector to produce a realistic failure, then runs the same Claude-investigation logic being developed in PR #651. Delete once a good prompt is found. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
✅ Deploy Preview for rp-cloud ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
Warning Review limit reached
Next review available in: 12 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
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 |
JakeSCahill
changed the title
1 participant
Temporary, workflow_dispatch-only scratch workflow for iterating on the "Investigate failure with Claude" prompt being developed in #651. Not a real change to any existing workflow — no schedule, no PR trigger, doesn't touch the real cron.
Deliberately breaks a real selector on an ephemeral checkout to produce a realistic failure, then runs the same investigate-prompt logic so we can judge diagnosis/fix quality via real
gh workflow runexecutions.Delete this file (and this branch) once a good prompt is found — this is not meant to be a lasting addition to
main.