chore: untrack TODO.md - #83
Merged
Merged
Conversation
TODO.md is session coordination, not repo documentation. Nothing in the repo reads it. No README, Makefile, workflow or test references it. It also named internal-only files, which is what surfaced it. Two of those references had been public since May. The file stays in the working tree at 6703 bytes and is now ignored, so it keeps its internal pointers. Those pointers are correct content for a private file. Sanitising them would strip the value it has locally. This matches how the repo already treats WORKING.md, SESSION_LOG.md, memory/ and notes/.
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
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.
TODO.mdis session coordination, not repo documentation.Why it goes
WORKING.md,SESSION_LOG.md,memory/andnotes/are all ignored.What happens to the file
It stays in the working tree at 6703 bytes and becomes gitignored. It keeps its internal pointers, because those are correct content for a private file. Sanitising them would strip the value it has locally.
Not fixed by this
The historical blobs still contain the old content. Removing those needs a history rewrite, which is out of scope here.
470 passed, 1 skipped.