fix(contract): preserve actionable Git resolver warning codes - #46
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Team Run ID: 📒 Files selected for processing (3)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. WalkthroughThe change adds recognized Git snapshot-resolution warning codes to the DiffGraph schema and structural warning handling. Structural JSON now preserves codes such as ChangesResolution warning codes
Estimated code review effort: 2 (Simple) | ~10 minutes Merge Risk: ⚪ Minimal · up to Structural JSON now retains supported Git resolution warning codes for consumers, with coverage for invalid base references and pathspecs outside the repository. No concrete current-head merge risk remains. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
Full details: Docstring CoverageExplanation Docstring coverage is 20.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 5 functions across 2 files. (1 skipped: 1 unsupported.)
✨ Finishing Touches 💡 1📝 Generate docstrings 💡
🧪 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 |
|
@coderabbitai review |
✅ Action performedReview finished.
|
Summary
Part of #21
Remaining #21 work is the broader end-to-end coverage of any unimplemented Git snapshot edge cases; this PR specifically makes already-detected resolver failures actionable to artifact consumers without detail-string parsing.
Validation
python3 -m pytest tests/test_structural.py -k 'invalid_ref_warning_code or scoped_pathspec_warning_code' -q\n-python3 -m pytest tests/test_git_snapshot.py -q\n-python3 -m pytest -qSummary by CodeRabbit
New Features
Bug Fixes
UNKNOWNcode when applicable.