Ignore the root tasks/ scratch directory - #1950
Open
EJTison wants to merge 1 commit into
Open
Conversation
Process notes written while working (todo lists, plans, specs) land in tasks/ and shouldn't ride along into feature PRs. Anchored to the repo root so it can't swallow the unrelated tasks/ source directories under pages/ and src/. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Contributor
Bundle sizes [mpdx-react]Compared against 0a0f7c3 No significant changes found |
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.
Description
Adds
/tasks/to.gitignore.Development process files — todo lists, plans, specs — get written to a root-level
tasks/directory while working, and they shouldn't ride along into feature PRs. This came up while building #1949:tasks/todo.mdshowed as untracked and had to be avoided by staging each file by hand, which is easy to get wrong.Why
/tasks/and nottasks/The leading slash anchors the pattern to the repo root. Without it, gitignore matches a directory of that name at any depth, which would also cover two unrelated source directories:
pages/accountLists/[accountListId]/tasks/src/lib/tasks/Files already committed there would keep tracking either way, but any new file added to them would be silently ignored — a confusing failure to run into later. Anchoring avoids that entirely.
Testing
git check-ignore -v tasks/todo.md→ matches.gitignore:60:/tasks/git check-ignoreon a hypothetical new file inpages/accountLists/[accountListId]/tasks/and insrc/lib/tasks/→ not ignored, both still trackgit statusreports no change to any currently-tracked file🤖 Generated with Claude Code