Uh oh!
There was an error while loading. Please reload this page.
feat: Phase 1.3 - Input validation and test files for stale issue management - #1750
Conversation
… management - manage-stale-issues.js: Add validateOptions() function to enforce validation rules - Validate --days as positive integer - Enforce minimum 7-day grace period before closure - Require at least one action (--label, --comment, --close) when not in dry-run mode - Added validation step in main() to check options before execution - review-meta-labels.js: Fix coverage calculation for all meta labels - Calculate coverage for every configured meta label (not just first) - Use META_LABELS array to ensure consistent analysis across all label types - Update analysis loop to process all labels in consistent manner - Add comprehensive test files for both scripts - manage-stale-issues.test.js: 20 tests covering validation, options, grace period - review-meta-labels.test.js: 20 tests covering coverage, recommendations, reporting - All tests passing (30/30) Closes: #1728 Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
Warning Review limit reached
Next review available in:24 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. 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: Repository YAML (base), Organization UI (inherited) Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (4)
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 |
✅ Template check passed after update. Thanks for fixing the PR description. |
⏱️ Aging and SLA annotation
Maintained by project-meta-sync workflow. |
🔍 Reviewer Summary for PR #1750CI Status: ✅ Recommendations
|
| const labelCount = 0; | ||
| const percentage = | ||
| totalIssues > 0 |
There was a problem hiding this comment.
Fixed in commit cf18f02: Replaced ternary condition with direct assignment. The test now directly assigns instead of evaluating a false guard condition.
🤖 Addressed by Claude Code
Uh oh!
There was an error while loading. Please reload this page.
Linked issues
Closes#1728
Changelog
Added
manage-stale-issues.test.js: Comprehensive test suite for stale issue management with 20 testsreview-meta-labels.test.js: Comprehensive test suite for meta label audit with 20 testsChanged
manage-stale-issues.js: AddvalidateOptions()function with validation rules--daysas positive integerreview-meta-labels.js: Fix coverage calculation to process all meta labels consistentlyMETA_LABELS.forEach()instead of ad-hoc trackingChecklist (Global DoD / PR)
Summary
Addressing outstanding CodeRabbit feedback for Phase 1.3 issue maintenance scripts. Added input validation for manage-stale-issues.js and fixed meta label coverage calculation in review-meta-labels.js with comprehensive test coverage.
Quality Checks