feat: add STP→tests cross-reference to CodeRabbit config - #148
Conversation
|
Warning Review limit reached
Next review available in: 54 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: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThis PR modifies .coderabbit.yaml. It enables review details and adds stps/** path instructions covering meaningful versus cosmetic STP changes, test mismatch and coverage-gap reporting, and non-blocking advisory behavior. It also links the RedHatQE/openshift-virtualization-tests repository for test cross-referencing. ChangesCoderabbit Configuration Update
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
Suggested labels: Suggested reviewers: 🚥 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 |
|
Report bugs in Issues Welcome! 🎉This pull request will be automatically processed with the following features: 🔄 Automatic Actions
📋 Available CommandsPR Status Management
Review & Approval
Testing & Validation
Cherry-pick Operations
Branch Management
Label Management
✅ Merge RequirementsThis PR will be automatically approved when the following conditions are met:
📊 Review ProcessApprovers and ReviewersApprovers:
Reviewers:
Available Labels
AI Features
Security Checks
💡 Tips
For more information, please refer to the project documentation or contact the maintainers. |
Add path_instructions for stps/** that flags meaningful STP changes (scenarios, goals, criteria, scope) for potential test impact in RedHatQE/openshift-virtualization-tests. Cosmetic changes (typos, formatting) are skipped. Key behaviors: - Greenfield STPs (no existing test refs) skip cross-ref entirely - Confirmed misalignment with existing tests: HIGH (informational) - New scenarios without tests / unconfirmed alignment: MEDIUM advisory - Cross-ref notice is non-blocking (STPs are source of truth) - Template files (stps/stp-template/) excluded Also adds linked_repositories pointing to the tests repo and enables review_details for linked-repo visibility. Signed-off-by: rnetser <rnetser@redhat.com> Co-authored-by: Cursor <cursoragent@cursor.com> Assisted-by: Claude <noreply@anthropic.com> Co-authored-by: Cursor <cursoragent@cursor.com>
cafb8bc to
76293a4
Compare
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
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 @.coderabbit.yaml:
- Around line 70-100: The advisory CrossReference review path in the CodeRabbit
configuration must not use request_changes_workflow. Update the relevant
workflow setting near the existing configuration at line 18 to disable
request_changes_workflow or select a supported non-review reporting path, while
preserving the non-blocking behavior described for the CrossReference notices.
🪄 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: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: f66cccb1-e05e-4b2c-b2b5-daccd5f4a42f
📒 Files selected for processing (1)
.coderabbit.yaml
|
/approve |
5 participants
Summary
Adds a cross-reference mechanism to CodeRabbit so that meaningful STP changes flag potential test impact in
RedHatQE/openshift-virtualization-tests.This is the reverse link — the tests repo already has a
linked_repositoriesentry pointing here for STP-to-test traceability. This PR adds the design-docs → tests direction.Changes
path_instructionsforstps/**When an STP is modified, CodeRabbit classifies the change as meaningful or cosmetic:
For meaningful changes, it checks the linked tests repo:
The cross-reference notice is non-blocking — STPs are the source of truth and tests catch up in follow-up PRs.
linked_repositoriesLinks to
RedHatQE/openshift-virtualization-testsso CodeRabbit can look up existing test coverage.review_details: trueEnables linked-repo context visibility in PR reviews (mirrors the tests repo config).
Template exclusion
Files under
stps/stp-template/are excluded from the cross-ref check.Made with Cursor
Summary by CodeRabbit