gitignore / glob / tracked review
Separate gitignore globs, exceptions, and tracked state
Review glob meaning, negation patterns, already tracked files, and directory scope separately. Prepare a correction proposal without writing to the repository.
Four ignore boundaries
Pattern evaluation and tracked state are different. Adding an ignore rule does not automatically untrack an existing file.
*.log = glob exclusion; negation = include exception; tracked.txt = tracked remains; tmp/ = directory scope| Category | Review |
|---|---|
| glob-exclusion | Check that a glob such as *.log excludes only the intended scope. |
| negation-exception | Check that a negation exception matches parent exclusions and order. |
| tracked-file | An already tracked file stays tracked; a separate approved action is required. |
| directory-only | A trailing slash such as tmp/ is reviewed as directory scope. |
Safe correction requests
- Record the pattern and target path.
- Choose glob, negation, tracked, or directory.
- Separate expected results from tracked differences.
- Apply a proposal only after human review.
This guide does not write .gitignore or run git commands. It does not upload a repository; use synthetic cases only.
Review cases
| case | decision | request |
|---|---|---|
glob-exclusion | exclude | Confirm scope before changing the glob. |
negation-exception | include-exception | Confirm exception order and parent path. |
tracked-file | tracked-remains | Do not confuse ignore rules with untracking. |
directory-only | directory-scope | Confirm files are not accidentally excluded. |
unsupported-repository-write | reject | Reject a request requiring repository write. |
Do not send a repository
Do not paste a real repository, secret, or token. Use synthetic cases and follow the existing approval process for real changes.