chore: remove stray scratch/debug files committed to develop - #1450
chore: remove stray scratch/debug files committed to develop#1450seonghobae wants to merge 5 commits into
Conversation
plan.md, test_parse.py, test_parse2.py, test_parse3.py, and frontend/src/components/NetworkGraph.tsx.out are ad-hoc planning notes, manual debug scripts, and a stray build-output copy that were accidentally committed to the protected default branch. None are referenced by the backend/frontend test suites or CI. Removing them also stops every still-open PR whose branch predates their addition from showing a misleading 'this PR deletes N files' diff against develop (e.g. #1287).
|
Warning Review limit reachedNext included review available in 54 minutes. View limit detailsLimit details: You’ve used the included review currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Review configuration: ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Team Run ID: 📒 Files selected for processing (4)
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 |
There was a problem hiding this comment.
Devin Review found 1 new potential issue.
⚠️ 1 issue in files not directly in the diff
⚠️ Literal percent sequences corrupt attachment names
When an attachment name contains URL-like percent text, unquote decodes it although MIME filenames are already decoded. Names can truncate at decoded slashes or select the wrong parser.
|
PR governance metadata gate is not ready for
|
|
Supersession provenance update (2026-09-03): #1523 has been closed only after exact comparison proved its entire valid delta is carried here. Both PRs were based on No #1523 check/review evidence transfers to this head. #1450 remains subject to fresh exact-head protected checks, review-thread state, and qualifying post-last-push approval before merge. |
|
@coderabbitai review 현재 exact head |
🧩 Analysis chain🏁 Script executed: #!/bin/bash
set -euo pipefail
base="042b0c70531b229af3acbd0421a2f23098d848b3"
head="3f8b0cdafcba27d595fd13c125457bbf4b8df484"
echo "== Checked-out HEAD =="
git rev-parse HEAD
echo "== Commit metadata =="
git show -s --format='%H%n%P%n%s' "$head"
echo "== Exact name-status diff =="
git diff --name-status "$base" "$head"
echo "== Exact stat =="
git diff --stat "$base" "$head"
echo "== Deleted file contents at base =="
for path in plan.md test_parse.py test_parse2.py test_parse3.py; do
echo "---- $path ----"
git show "$base:$path" | nl -ba
done
echo "== Repository references to removed paths, excluding Git metadata =="
rg -n -i -C 2 \
'(?:^|[/"` ])(?:plan\.md|test_parse(?:2|3)?\.py)(?:$|[/"` :])' \
-g '!**/.git/**' . || true
echo "== Relevant repository automation/config files =="
fd -HI -t f \
'^(Makefile|README(\.md)?|pyproject\.toml|pytest\.ini|tox\.ini|setup\.cfg|package\.json|\.github)$' \
. 2>/dev/null | sort || trueLength of output: 1944 🏁 Script executed: #!/bin/bash
set -euo pipefail
base="042b0c70531b229af3acbd0421a2f23098d848b3"
head="3f8b0cdafcba27d595fd13c125457bbf4b8df484"
echo "== Deleted file contents at base =="
for path in plan.md test_parse.py test_parse2.py test_parse3.py; do
echo "---- $path ----"
git show "$base:$path" | awk '{ printf "%6d\t%s\n", NR, $0 }'
done
echo "== Tracked references at base =="
git grep -n -i -E '(^|[^[:alnum:]_.-])(plan\.md|test_parse\.py|test_parse2\.py|test_parse3\.py)($|[^[:alnum:]_.-])' "$base" -- \
':!plan.md' ':!test_parse.py' ':!test_parse2.py' ':!test_parse3.py' || true
echo "== Tracked references at exact head =="
git grep -n -i -E '(^|[^[:alnum:]_.-])(plan\.md|test_parse\.py|test_parse2\.py|test_parse3\.py)($|[^[:alnum:]_.-])' "$head" || true
echo "== Root-level tracked files at base =="
git ls-tree --name-only "$base" | sed -n '1,160p'
echo "== Root-level tracked files at exact head =="
git ls-tree --name-only "$head" | sed -n '1,160p'Length of output: 9529
삭제된 Python 파일은 이 cleanup delta에서 제품 동작, 테스트 실행, 또는 자동화 구성에 영향을 주는 문제를 찾지 못했습니다. 요청에 따라 diff 밖 attachment-parser 항목은 검토 범위에 포함하지 않았습니다.
|
Current exact-head state — 2026-09-07
develop@042b0c70531b229af3acbd0421a2f23098d848b33f8b0cdafcba27d595fd13c125457bbf4b8df484This PR removes
plan.md,test_parse.py,test_parse2.py, andtest_parse3.py. The historical description also namedfrontend/src/components/NetworkGraph.tsx.out, but that path is not part of the current exact-head diff. Thetest_parse*.pyfiles are one-offtext_safetydebugging scripts that mutatesys.pathand call internal helpers outside the repository's normalbackend/tests/ownership.Current evidence
Repository-owned exact-head workflows are terminal-success for Application CI
33607711416, Security Scan33607710995, SAST Semgrep33607711068, Bandit33607711130, Dependency Review33607711125, and Docker33607711489. The exact-headcoverage-evidencecheck is also terminal-success.All inline review threads are clear. Existing Devin submissions are
COMMENTED; its later MIME percent-decoding note is outside this four-file cleanup delta and remains owned by the attachment-parser repair lane rather than being copied here.The remaining required central evidence is not GREEN on this unchanged head:
strixis completed/cancelled,noema-reviewis completed/failure, andopencode-reviewis completed/cancelled. Those historical exact-head results came from central owner controls that have since changed; they are not Naruon source findings and they are not passing evidence.This PR was moved from Draft to Ready for independent review without changing the source SHA so review admission is no longer blocked by Draft state. Ready is not merge authorization. A fresh central evaluation or qualifying current-head approval must still occur, and every then-live required gate must be satisfied on this same exact head before merge.
Do not create a no-op requeue commit, transfer predecessor evidence, self-approve, dismiss reviews, weaken protection, or use admin/bypass merge.