gitignore_rules

Git negation rules fail when a directory is ignored because Git skips the directory entirely, preventing any un-ignore patterns from being evaluated. Changing the directory-ignore to ignore its contents instead allows negation rules to apply to specific files within it.

Fixing broken .gitignore patterns requires auditing structural errors like directory-ignores blocking negations. The file is corrected by changing directory rules to content rules, then verified using `git check-ignore` to confirm proper file tracking.

The `git check-ignore` command verifies ignore status by testing specific file paths against the active .gitignore rules. It outputs whether a file matches an ignore pattern, confirming whether structural fixes successfully restored intended tracking behavior.

You cannot un-ignore specific files if the parent directory itself is ignored. You must first change the directory-ignore pattern to a wildcard content pattern, which then allows subsequent negation rules to target specific files within that directory.

Auditing a complex .gitignore file involves scanning for structural pitfalls where directory-ignores silently block negation rules. Correcting these errors ensures intended files are tracked, and verification via `git check-ignore` confirms the applied fixes resolve unexpected behavior.

A common .gitignore pitfall is ignoring a directory with a trailing slash, which prevents Git from descending into it and blocks any negation rules for files inside. Replacing the directory rule with a wildcard content rule resolves this tracking limitation.