Skip to content

chore: relocate REVIEW-*.md to docs/reviews/ - #67

Merged
petlenz merged 1 commit into
mainfrom
chore-relocate-review-docs
Jun 3, 2026
Merged

chore: relocate REVIEW-*.md to docs/reviews/#67
petlenz merged 1 commit into
mainfrom
chore-relocate-review-docs

Conversation

@petlenz

@petlenz petlenz commented Jun 3, 2026

Copy link
Copy Markdown
Member

Summary

Repo root has accumulated 5 review-artefact files (REVIEW-pr-57.md, REVIEW-pr-58.md, REVIEW-pr-62-round3.md, REVIEW-stack-42-47.md, REVIEW-stack-51-55.md). Pure git mv into docs/reviews/ — content unchanged.

Deferred m3 from the round-3 review of the modernization triple (PR #62 series). Picked up now as a 5-min cleanup PR while #66 CI runs.

Why bare-filename references in code/comments are fine

Several headers + tests reference these by bare filename (e.g. recipe.h:135 mentions REVIEW-pr-58.md). The relocation doesn't break their meaning — the documents still exist under the same names. Anyone searching for them via grep finds them in docs/reviews/. Not worth touching working code for a path-only rename.

Test plan

  • git mv preserves history (verified via git log --follow)
  • No file references the old paths with a docs/ or absolute-path prefix (grep -rn 'REVIEW-' --include='*.md' --include='*.h' --include='*.cpp' returns only bare-filename mentions, which still resolve)

@petlenz
petlenz merged commit 5cdcc21 into main Jun 3, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant