fix(review): drop pre-merge checks #64
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!64
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/drop-pre-merge-checks-63"
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
.auto_review.yamlpre_merge_checkssupport and delete the custom pre-merge prompt/schema path.Verification
nix develop -c cargo nextest run -p ar-review full_source_only_git_diff_with_no_findings_omits_pre_merge_checks_without_request_changes custom_pre_merge_checks_are_not_evaluated_or_emitted_for_no_finding_reviewsnix develop -c cargo nextest run -p ar-review -p ar-prompts -p ar-orchestrator --no-tests=passnix develop -c cargo fmt --all -- --checknix develop -c cargo clippy --workspace --all-targets -- -D warningsCloses #63.
This PR removes the pre-merge checks from the review process, including both built-in and custom checks. The changes involve deleting related code, schemas, and documentation references. The PR appears safe to merge, but users should be informed about the removal of pre-merge checks and update their configurations accordingly.
Walkthrough
Configuration Changes
pre_merge_checksfrom.auto_review.example.yaml..forgejo/pull_request_template.mdto reflect the removal of bot-run pre-merge checks.Code Changes
run_review_jobindispatcher.rs.pre_merge_custom.jsonschema and related code inar-prompts.pre_mergeandpre_merge_llmmodules fromar-review.Documentation Updates
CHANGELOG.mdto document the removal of pre-merge checks.README.md,USER-GUIDE.md, and other documentation files.Testing
Pre-merge checks
@auto_review re-review
Queued a fresh review at
8f74200aee. Watch the commit-status badge for progress.This PR removes the pre-merge checks from the review pipeline, including both built-in and custom checks. The changes appear safe to merge, but users should be informed about migrating these checks to CI or static analysis tools.
Walkthrough
pre_merge_checksfrom.auto_review.example.yamland related documentation.pre_merge_custom.json,pre_merge_custom.rs, and related logic indispatcher.rsandpipeline.rs.