Repository navigation
docs(skills): warn address-comments about stale git-blame fixup targets - #148
Conversation
git blame names whichever commit last touched a line as of the current tree, but in a multi-round review-response session an earlier round's own fixup can have already rewritten the exact lines a new fix touches, without blame's answer reflecting that a LATER commit also touched the region. A fixup against the blame-named commit then conflicts on autosquash. Recurred 6 times across 3 review rounds on PR #131/#132, always resolved by retargeting to the actual last in-branch commit touching the file (verified via git diff before recommitting), never by falling back to a plain non-fixup commit. Also refines Step 8's blanket "abort and escalate" instruction: a stale-target conflict and a mechanical import-list merge are both safe to self-resolve (no judgment call about what the code should do); only a genuine content clash -- two different intended changes to the same logic -- still escalates. MrReasonable <4990954+MrReasonable@users.noreply.github.com>
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 2 minutes Limit details: You’ve used all 1 included review currently available under your plan. You completed 96 included PR reviews in the past 7 days; at that activity level, included reviews refill at 1 review per hour. 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: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
Comment |
1 participant
Summary
git blamenames whichever commit last touched a line as of the CURRENT tree, but a later in-branch commit may have already rewritten that region without blame reflecting it -- a fixup committed against blame's answer then conflicts on autosquash. Recurred 6 times across 3 review-response rounds on PR MCP: write-capable tools for the operations an agent actually does every session #131/feat(mcp): write-capable tools for create_lead, dismiss_lead, apply_record, cv_run, cv_signoff #132, always resolved by retargeting.git log --oneline <merge-base>..HEAD -- <file>for the last in-branch touch,git diff <candidate> -- <file>to confirm the hunk already matches) and guidance for splitting a fixup across files with different correct targets.Test plan
.rulesync/skills/address-comments/SKILL.md(the canonical source); no generated output needs regenerating/committing.