Remove AI triage frontend call logic and cleanup AI look#1610
Remove AI triage frontend call logic and cleanup AI look#1610prathmeshpatel merged 1 commit intomainfrom
Conversation
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
eec1488 to
cffa855
Compare
1ed3468 to
9995255
Compare
9995255 to
fb62ff9
Compare
cffa855 to
7b6571d
Compare
fb62ff9 to
925f269
Compare
7b6571d to
3421fa3
Compare
925f269 to
f2b837a
Compare
7c2ec0a to
bc79e76
Compare
6a1d050 to
a825d9b
Compare
bc79e76 to
55c03d6
Compare
55c03d6 to
16823f0
Compare
|
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: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (5)
WalkthroughThis pull request restructures AI triage functionality from a client-side context-generation model to a backend-driven mutation approach. Specifically: the 📝 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 |

TL;DR
Replaced client-side OpenRouter AI triage with backend Convex mutation calls for eval suite failure analysis.
What changed?
useCommitAiTriageanduseOverviewAiTriagehooks with a singleuseCommitTriagehook that calls Convex backend mutations