$ show github/gitignore
This repository is a curated collection of .gitignore file templates for a wide range of programming languages, frameworks, editors, and operating systems. It serves as the source for GitHub's built-in .gitignore template chooser when creating new repositories. The repository is organized into root-level templates for common technologies, a Global/ directory for editor/OS-specific rules, and a community/ directory for specialized or versioned templates. Each file is a self-contained list of file patterns to exclude from version control, following best practices for the respective technology. The templates are maintained through community contributions and a stale PR workflow. While the repository contains no executable code, its value lies in the curated, accurate, and up-to-date ignore rules that help developers avoid committing unnecessary or sensitive files.
The LLM identified 3 files worth highlighting for reuse:
A comprehensive .gitignore template for Python projects. It covers byte-compiled files, distribution/packaging artifacts, virtual environments, testing/coverage output, Jupyter Notebook checkpoints, and many common Python tool caches. The rules are well-organized into commented sections, making it easy to understand and customize. This template is reusable for any Python project and demonstrates thorough knowledge of Python development artifacts.
An extremely detailed .gitignore template for Visual Studio and .NET projects. It covers user-specific files, build results for multiple architectures, NuGet packages, MSTest/NUnit outputs, ReSharper, NCrunch, and many other Visual Studio add-ons. The template is well-commented and organized, making it easy to selectively uncomment rules. It is the de facto standard for ignoring Visual Studio artifacts and is reusable across any .NET project.
A thorough .gitignore template for Unity game projects. It ignores library, temp, obj, build, and log directories, as well as Unity-specific files like meta files, crash reports, and Addressables content state. It also includes rules for JetBrains Rider, Visual Studio, and Gradle caches. The template is well-structured with comments explaining each section, making it easy to adapt. It demonstrates deep knowledge of Unity's build artifacts and is reusable for any Unity project.