Conversation
…d logging functionality
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 13 minutes and 12 seconds. ⌛ 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: Path: .coderabbit.yml Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 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 |
Why
Need to remove fragile cross-package imports in the db seed script while keeping the dependency graph safe
What
Closes: #404
Refactored the db seed script to stop relying on fragile cross-package wiring
Kept package dependencies aligned to avoid introducing cycles between db/api/utils
Fixed minor cleanup issues found during review (including message text consistency)
Updated lockfile to match dependency/export changes
Test Plan
Ran pnpm --filter @forge/db typecheck successfully
Ran pnpm install successfully
Verified the seed script resolves cleanly with no diagnostics
Confirmed no circular dependency warning remains from this change set
Checklist
db:pushbefore merging