feat(collab): cut collaboration over to metric results#196
Conversation
|
Warning Review limit reached
Next review available in: 47 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. 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: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (47)
✨ 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 |
72d242c to
49e55a8
Compare
ktursunov
left a comment
ktursunov
left a comment
There was a problem hiding this comment.
Please fill in the gaps in coverage
49e55a8 to
ad9f9f3
Compare
Hash-to-hue series coloring collided (all collaboration tools landed in one blue band) on top of greyscale chart tokens. Known tools now map to vendor-brand tokens tuned per ground, unknown seeds fall back to shadcn categorical chart tokens in sorted order; composition legends switch to tenth precision when integer shares would show a nonzero part as 0%. Signed-off-by: Aleksandr Barkhatov <pm@aleks.bar>
Surfaces re-deriving standings from raw stats produced contradictory verdicts: quartile chips flattering all-zero pools, good-coloring next to Bottom 25%, favorability-signed gaps reading as position on lower-is-better metrics. derivePeerStanding owns eligibility and both judgments; displays only map the result. Median-strict quartile rule, arithmetic gap sign, shared inset-shadow status stripe, KPI tile explanation row. Signed-off-by: Aleksandr Barkhatov <pm@aleks.bar>
Mirrors the git/AI cutovers: one MetricGroup with 19 collab.* keys, modality summary cards with dimension breakdowns replace the trend charts, legacy messaging panel and summary strip die. Heatmap bullet columns keep the legacy collab feed until team surfaces migrate. Signed-off-by: Aleksandr Barkhatov <pm@aleks.bar>
ad9f9f3 to
0016050
Compare
2 participants
Cuts the Collaboration dashboard group over to
POST /v1/metric-results, mirroring the git and AI cutovers.MetricGroupwith 19collab.*keys; legacy messaging panel and summary strip removedCloses constructorfabric/insight#1703