fix(review): approve clean re-reviews #53
No reviewers
Labels
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Slipstream/auto_review!53
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/clean-rereview-approval"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Verification
Closes #52.
This PR updates the review mapping logic to post an
Approvedreview for clean Auto Review runs, addressing issue #52. The changes appear well-documented and tested, making them safe to merge.Walkthrough
Approvedreview.output_to_review_requestfunction to map clean review outputs toApprovedreviews.Approvedreview.Pre-merge checks
Linters
This PR updates the review mapping logic to post an
Approvedreview for clean re-reviews, addressing issue #52. The changes appear well-structured and include necessary test updates, but ensure the logic aligns with the intended behavior.Walkthrough
Approvedevents instead ofComment.Approvedreview event.Pre-merge checks
Linters
@ -12,4 +12,4 @@/// - Each finding becomes one inline `ReviewComment` anchored at/// `new_position = line_start`. Multi-line ranges are rendered as a/// `**Lines N–M:**` prefix in the body since Forgejo's per-line position/// schema doesn't carry an end line.🟡 Warning: The logic for determining the review event has changed. Ensure that this logic aligns with the intended behavior for handling clean reviews.
Addressed by documenting the intent directly at the event-mapping seam: clean outputs intentionally post
Approvedbecause Forgejo branch protection treats that as superseding this bot's staleRequestChangesafter a clean re-review. Focused verification passed:nix develop --command cargo nextest run -p ar-review clean_review_output_posts_approval any_error_severity_promotes_to_request_changes only_warnings_and_notes_stay_comment.This PR updates the review mapping logic to post an
Approvedreview for clean re-reviews, addressing issue #52. The changes are well-documented and tested, ensuring that clean re-reviews can supersede staleRequestChangesreviews. The PR appears safe to merge.Walkthrough
Approvedreview for clean re-reviews, which addresses issue #52.output_to_review_requestfunction to post anApprovedreview when there are no findings, ensuring clean re-reviews supersede staleRequestChangesreviews.clean_output_is_an_approved_review_to_supersede_stale_request_changesto verify the new behavior.clean_review_output_posts_approvalto ensure that clean review outputs result in anApprovedreview event.Pre-merge checks
Linters