chore: untrack the plan-review scratch note - #14
Merged
Conversation
plans/plan_review_20260718.txt was added to the tree by mistake in #13: that commit staged with `git add -A`, which swept up a working note that had deliberately sat untracked. It is neither a plan under the plans/{completed,history} convention nor English-language repository content. Remove it from version control. The file stays on disk, untracked, as it was before.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Removes
plans/plan_review_20260718.txtfrom version control. It stays on disk,untracked, exactly as it was before.
Why
The file was committed by accident in #13. That commit staged with
git add -A,which picked up a working note that had been left untracked on purpose since July.
It is a personal scratch note, not repository content: it is not a plan under the
plans/{completed,history}naming convention, and it is not English.Nothing else in #13 is affected — the
errcheckcleanup is unchanged and stays.Note on recovery
Removing the file from
HEADdoes not erase it from history; it remains reachablein the #13 merge commit. That is acceptable here since the content is only working
notes, but if it should not be in the history at all, that needs a history rewrite
of
mainand is a separate, deliberate decision.Optional follow-up, not included
A
.gitignoreentry such asplans/plan_review_*.txtwould stop this class of filefrom being staged again. Left out because it is a repository-convention decision,
not part of undoing the mistake.