The .gitignore file is a core component of Git's tracking model that specifies intentionally untracked files the version control system should ignore. Understanding how Git tracks files is essential to using .gitignore effectively. Git manages files in three states: tracked (files that were in the last snapshot or are staged), untracked (files not in the last snapshot and not staged), and ignored (files explicitly matched by .gitignore patterns that Git will not track). Crucially, .gitignore only affects untracked files. If a file is already tracked by Git, adding it to .gitignore will not cause Git to stop tracking it. The file must first be removed from the index with "git rm --cached" before the ignore pattern takes effect.

Gitignore pattern syntax uses glob matching, a pattern-matching notation distinct from regular expressions. An asterisk (*) matches any sequence of characters within a single path component. A double asterisk (**) matches across directory boundaries: **/logs matches a "logs" directory anywhere in the tree, and logs/** matches everything inside a "logs" directory. A question mark (?) matches any single character. Square brackets define character classes: [abc] matches a, b, or c. A leading slash anchors the pattern to the directory containing the .gitignore file, preventing it from matching in subdirectories. A trailing slash matches only directories. An exclamation mark (!) negates a pattern, re-including a file that would otherwise be ignored, though it cannot re-include a file in an ignored directory.

Git processes .gitignore files with a defined precedence hierarchy. Patterns from the command line (via git add -f or git check-ignore) have the highest priority. Next come patterns from the .gitignore file in the same directory as the path being checked, then patterns from parent directories up to the repository root. Repository-level patterns in .git/info/exclude apply only to the local clone and are not shared with collaborators. Finally, patterns from the file specified by the core.excludesFile configuration (typically ~/.gitignore_global) apply to all repositories for the current user. This hierarchy allows project-wide patterns in the root .gitignore while permitting directory-specific overrides deeper in the tree.

Common .gitignore patterns address several categories of files that should not be version-controlled. Build artifacts (dist/, build/, *.o, *.class) are generated from source code and can be reproduced. Dependencies (node_modules/, vendor/, venv/) are installed by package managers and are defined by lockfiles. Environment configuration (.env, .env.local) contains secrets like API keys and database passwords that must never be committed. IDE and editor settings (.vscode/, .idea/, *.swp) are personal preferences that vary between developers. OS-specific files (.DS_Store, Thumbs.db) are system metadata irrelevant to the project. Log files (*.log, logs/) and temporary files (*.tmp, *.cache) are transient data that clutters repositories and can grow to significant sizes.