Fix #505: include rename previous paths in PR trust classification#510
Fix #505: include rename previous paths in PR trust classification#510marktech0813 wants to merge 1 commit into
Conversation
|
Important Review skippedNo new commits to review since the last review. ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
📝 WalkthroughWalkthroughThe workflows now collect paginated pull-request file data through the REST API, including rename source paths. Classification documentation and tests cover core-path rename handling. ChangesRename-aware classification
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 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 |
e7a1aa4 to
4713af1
Compare
…ation gh pr view --json files omits previous_filename, so git mv of a CORE_GLOBS path could classify as code and bypass trust-gate/auto-merge blocks. Switch workflows to REST pulls/files (which includes previous_filename) and feed both current and previous paths into classify/core-touched.
4713af1 to
43187d8
Compare
|
@coderabbitai review |
✅ Action performedReview finished.
|
Summary
Fixes #505 — trust-gate / auto-merge / related workflows now list changed files via REST
pulls/{n}/files, which includesprevious_filenameon renames, and pass both paths intopr_botclassification.This closes the
git mvbypass of CORE_GLOBS detection.Test plan
pytest tests/test_pr_bot.py -k renamesrc/vouch/http_server.pyfails trust-gate as coreSummary by CodeRabbit