Non-Blocking Review Concern: File rename from code→docs classified as doc-only
Source: pre-push whole-codebase review
Location: .github/workflows/claude-blocking-review.yml:137
Date: 2026-04-18
What was flagged
gh pr diff --name-only reports only destination paths for renames. A rename from src/foo.py → docs/foo.md (unusual but possible) would appear as only docs/foo.md, causing the PR to be classified doc-only and skip review, even though the diff contains significant code deletion. Low probability but a theoretical blind spot. Detecting this robustly would require parsing the full diff rather than --name-only.
Context
This issue was automatically created from a non-blocking concern identified
during pre-push whole-codebase review. It was flagged for tracking.
Created by lib-review-issues.sh
Non-Blocking Review Concern: File rename from code→docs classified as doc-only
Source: pre-push whole-codebase review
Location:
.github/workflows/claude-blocking-review.yml:137Date: 2026-04-18
What was flagged
gh pr diff --name-onlyreports only destination paths for renames. A rename fromsrc/foo.py→docs/foo.md(unusual but possible) would appear as onlydocs/foo.md, causing the PR to be classified doc-only and skip review, even though the diff contains significant code deletion. Low probability but a theoretical blind spot. Detecting this robustly would require parsing the full diff rather than--name-only.Context
This issue was automatically created from a non-blocking concern identified
during pre-push whole-codebase review. It was flagged for tracking.
Created by lib-review-issues.sh