docs(EC-1999): document testing expectations for collection changes - #1815
Conversation
Expand the "Add a new collection" entry in AGENTS.md to clarify that collections are metadata-only and don't need new tests. make conventions-check validates dependency-collection constraints. New rules alongside a collection still need _test.rego coverage.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan includes up to 1 review per rolling hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe collection creation guidance now specifies metadata-only definitions, removes collection-specific test requirements, identifies CLI and conventions-check validation, and retains test coverage for accompanying rules. ChangesCollection guidance
Estimated code review effort: 1 (Trivial) | ~2 minutes Merge Risk: ⚪ Minimal · up to This is a localized documentation update with no actionable merge-blocking risk remaining after normal checks. 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 |
|
🤖 Finished Review · ✅ Success · Started 8:14 AM UTC · Completed 8:28 AM UTC Commit: |
Codecov Report✅ All modified and coverable lines are covered by tests.
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
ReviewFindingsMedium
Low
Labels: PR is a documentation-only change to AGENTS.md |
|
/lgtm |
|
🤖 Finished Retro · ✅ Success · Started 8:28 AM UTC · Completed 8:40 AM UTC Commit: |
Retro: PR #1815 — docs(EC-1999): document testing expectations for collection changesVerdict: The end-to-end pipeline worked. A retro agent identified a real documentation gap from PR #1766, filed issue #1776, and the system produced a technically correct fix via PR #1777. A human (BohdanMar) later created PR #1815 with minor editorial improvements and merged it, explicitly superseding the agent's PR. The review agent on PR #1815 performed well — correctly flagging the protected-path governance requirement, producing reasonable technical-accuracy and style findings, and using the challenger/adversarial verification pattern to appropriately downgrade findings that didn't hold up under scrutiny. Timeline
Evidence for existing issues (no new proposals needed)
What went well
|
Summary
make conventions-checkvalidates dependency-collection superset constraints_test.regocoverageResolves EC-1999
Supersedes #1777