From cebe67e832f70f428ec12eb097c4350878714b8b Mon Sep 17 00:00:00 2001 From: ghartuv Date: Thu, 19 Nov 2026 14:56:00 +0200 Subject: [PATCH] Add rpms.lock.yaml to the protected paths used by the review agent This triggers enhanced review scrutiny when rpms.lock.yaml is modified, making the review agent more likely to examine structural changes (like header removal) beyond simple version bumps. Ref: https://redhat.atlassian.net/browse/EC-2358 Assisted-by: gpt-6-sol --- .fullsend/customized/harness/review.yaml | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/.fullsend/customized/harness/review.yaml b/.fullsend/customized/harness/review.yaml index 243d5c72de..eabab66ede 100644 --- a/.fullsend/customized/harness/review.yaml +++ b/.fullsend/customized/harness/review.yaml @@ -23,5 +23,11 @@ readonly_repo: true env: runner: REVIEW_FINDING_SEVERITY_THRESHOLD: "high" + # Upstream recommends keeping these identical: the review agent reads the sandbox value, + # and the post-script reads the runner value. + REVIEW_PROTECTED_PATHS: | + rpms.lock.yaml sandbox: REVIEW_FINDING_SEVERITY_THRESHOLD: "high" + REVIEW_PROTECTED_PATHS: | + rpms.lock.yaml