Conversation
|
Warning Review limit reached
Next review available in: 45 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 ignored due to path filters (1)
📒 Files selected for processing (5)
📝 WalkthroughWalkthroughRemoved the admin.pip Typer CLI module and its registration in pyproject.toml. Updated ScopeName typing in pytest_params: params.py adds pytest >= 9.1.0 import support and updates the scope parameter annotation; params.pyi renames the _ScopeName type alias to ScopeName and updates the corresponding annotation. ChangesAdmin CLI Removal
ScopeName Typing Update
Estimated code review effort: 2 (Simple) | ~10 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ 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 |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@src/pytest_params/params.py`:
- Around line 11-16: Update the version-gated import in params.py so the pytest
>= 9.1.0 branch uses the public pytest.ScopeName type instead of importing
ScopeName from the private _pytest.scope module. Keep the existing fallback
behavior for older pytest versions, and adjust the conditional import logic
around the ScopeName alias accordingly.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: fa54ec80-99c8-4b40-83b9-4cbf30d418de
⛔ Files ignored due to path filters (1)
uv.lockis excluded by!**/*.lock
📒 Files selected for processing (4)
admin/pip.pypyproject.tomlsrc/pytest_params/params.pysrc/pytest_params/params.pyi
💤 Files with no reviewable changes (2)
- pyproject.toml
- admin/pip.py
Remove unused functions.
Pytest
9.1.0change 14137 (full changelog here) madepytest.ScopeNamepublic, which broke an import in this package.Fixed so it's compatible both with
9.1.0+and9.1.0-versions.Summary by CodeRabbit
Bug Fixes
Chores