Conversation
Acknowledges main's squash commit as an ancestor to prevent phantom conflicts on the next dev→main promotion.
…360) Closes the last-mile gap in the GitHub-issue → Quinn-triage → board pipeline. Two changes: 1. GitHub webhook handler now enriches inbound issue events with projectPath + projectSlug from projects.yaml (same resolution the sweep path already does). Without this, the board API rejects the create call. 2. SkillDispatcherPlugin fires _fileTriageOnBoard() in the onTerminal callback when a bug_triage skill completes successfully on a GitHub-sourced issue. POSTs to /api/board/features/create with the issue metadata + Quinn's triage summary. End-to-end: GitHub issue filed → webhook → bus → Quinn bug_triage → triage summary → auto-filed on automaker project board. No human intervention for triage. Co-authored-by: Automaker <automaker@localhost> Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
chore: back-merge main → dev
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
|
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 9 minutes and 52 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.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (4)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
1 participant
Summary
Test plan