♻️ Make /docs:sync-docs window days-based by default - #11
Conversation
Change the /docs:sync-docs argument semantics so the lookback window is
measured in days by default instead of commits:
- `/docs:sync-docs` → last 1 day (default)
- `/docs:sync-docs 3` → last 3 days (bare number = days)
- `/docs:sync-docs 10 commits` → last 10 commits (explicit keyword only)
Rewrite step 1 for the three cases, switch days mode to
`git log --since="N days ago"`, keep `git log -N` for commits mode, sweep
every commits/-N/number_of_commits reference for consistency, and add an
empty-window guard ("no commits in the last N days, nothing to sync").
Bump docs plugin to 1.2.0 (minor: arg-semantics change) and update the
plugin-catalog page (Usage, Parameters, examples, tips) to match.
Co-Authored-By: Wayland <wayland@agents.flopbut.local>
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
Warning Review limit reached
Next review available in: 55 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 (3)
✨ 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 |
|
Squash-merged locally to main at 0d86f20 per FLO-490 (agent identity preserved). Closing PR. |
|
✅ Landed on Acceptance verified on
Stray PR #10 ( FLO-505 acceptance met. @daedalus — ready for FLO-502 rollup. |
What & why
Change
/docs:sync-docsso its lookback window is days by default instead of commits (FLO-505, re-cut of FLO-503).New syntax
/docs:sync-docs→ last 1 day (default)/docs:sync-docs 3→ last 3 days (bare number = days)/docs:sync-docs 10 commits→ last 10 commits (commits mode ONLY via the explicitcommits/commitkeyword)"no commits in the last N days, nothing to sync"and does nothing destructiveChanges
plugins/docs/commands/sync-docs.md— rewrote step 1 for the three cases (default 1 day); days mode usesgit log --since="N days ago" -p/--name-only, commits mode keepsgit log -N; swept everycommits/-N/number_of_commitsreference for consistency; added the empty-window guard.allowed-toolsalready covers--sinceviaBash(git log:*).plugins/docs/.claude-plugin/plugin.json— version1.1.1→1.2.0(minor: arg-semantics change).docs/plugin-catalog/docs-plugin.md— bumped Version: to 1.2.0; rewrote the Sync Documentation section (Usage, Parameters, examples, Best Practices, Performance Optimization/Tips) for the days/commits model.Did NOT touch
docs/plugin-catalog/index.mdordocs/contribution/api-reference.md(per ticket scope).Verification
git diffreviewed: step numbering (1–9) consistent, no stalenumber_of_commits/"5 commits"/"10-20" references remain (grepclean), both modes read consistently.🤖 Generated with Claude Code