Repository navigation
Conversation
`_proof/` and `target-wt/` are ship-it evidence and local build output. They were showing up as untracked work on every checkout.
Tiny Code Reviewthe AI provider rate-limited the request This is advice, not a gate. Re-run with the |
unRekable
left a comment
There was a problem hiding this comment.
Code Review
🟡 1 finding (0 blocking).
The change adds two root-anchored ignore entries so local ship-it evidence and a stray worktree target directory stay off git status, following the existing /reports/ pattern; target-wt/ has no tracked content and is fine. The problem is /_proof/: it matches five files already tracked on main (_proof/README.md plus four PNGs). The rule does nothing to those tracked files, so their status noise remains, and any future proof writeup that follows the pattern that same README documents gets silently skipped by git add . with no error.
Residual risk
target-wt/is not created or documented by anything in the tree today, so the rule encodes a local convention; if the tooling's name drifts, a new stray directory will reappear as untracked noise.e2e/gate.jsonhasrelease_proof: "report"; if a release captain ever needs proof files from_proof/shipped with a change,git addwill now skip them and require-for a path outside the ignore.
|
|
||
| # UAT and design screenshots are outputs, not sources. | ||
| /reports/ | ||
| /_proof/ |
There was a problem hiding this comment.
_proof/README.md, inbox.png, inbox-unread.png, switcher.png, telegram-mute-bell.png). Ignore rules do not untrack them, so their modifications still show in git status, while any new proof writeup added next to them — the exact pattern that README documents — is silently left out of git add . and can disappear from a PR without an error. Smallest fix: make the tree agree with the rule in this PR by untracking the folder (git rm -r --cached _proof/), or keep the tracked baselines and scope the rule instead of ignoring the directory wholesale.
What changed and why
Local ship-it evidence under
_proof/and a straytarget-wt/directory were showing up as untracked work on every checkout. They are outputs, the same kind asreports/, and they stay on disk. Git now ignores them.Type
Platforms
Proof
No behavior change. Nothing for the lab to record.
Compatibility
No protocol or client change.
Risk and rollback
A proof folder someone meant to commit would be ignored. Revert this commit to track it again.
Release note
Local proof folders are no longer offered as untracked files.