Two Git Ignore Files You Likely Missed

Mihai Dinculescu recently published a short technical note on his personal development blog titled “Two Git Ignore Files Nobody Told Me About.” The post explains two lesser‑known mechanisms for excluding files from a Git repository that are not covered in most introductory guides. While the article is concise, it offers a practical overview of how these files can be used to keep a project’s history clean and to reduce merge conflicts.

The first file discussed is the repository‑specific `.git/info/exclude`, which functions like a local `.gitignore` but is not committed to the repository. Dinculescu highlights its usefulness for developers who want to ignore machine‑specific or IDE‑generated files without affecting teammates. The second file is the global ignore file, typically located at `~/.config/git/ignore` or referenced via the `core.excludesfile` configuration. The author demonstrates how setting this file can centralize ignore rules across all projects for a single user, simplifying workflow and ensuring consistency.

The blog post was shared on Hacker News, where it received four points and three comments. Readers praised the clarity of the explanation and noted that the information is valuable for teams looking to streamline their Git hygiene. The discussion was brief, suggesting that while the topic is niche, it resonates with developers who manage large codebases or collaborate across multiple environments.