gitignore: keep local planning notes out of the repo - #2
Merged
Conversation
Planning docs stay on the machine, like CLAUDE.md above them. A glob rather than a filename. This file ships, so an entry naming the thing being planned publishes the roadmap it was meant to keep local, and every future note would need its own published line.
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.
Planning docs stay local, like
CLAUDE.mdabove them.Uses a glob rather than a filename.
.gitignoreships, so an entry naming the thing being planned publishes the roadmap it was meant to keep local — and every future note would need its own published line.PLAN-*.mdmatches no tracked file (BUILD.md,README.md,WRITEUP.mdare the tracked.mdfiles).