# How to Create and Use Language-Specific .gitignore Templates from the GitHub Collection > Learn to use language-specific gitignore templates from GitHub. Copy files directly or combine with global templates to ignore editor and OS artifacts in your projects. - Repository: [GitHub/gitignore](https://github.com/github/gitignore) - Tags: how-to-guide - Published: 2026-02-24 --- **You can copy any language-specific .gitignore template directly from the github/gitignore repository root into your project, or combine root-level language files with global templates to ignore editor and OS artifacts across all repositories.** The github/gitignore repository maintains a curated collection of `.gitignore` templates for virtually every programming language, framework, and development environment. This open-source collection organizes language-specific .gitignore templates as standalone files in the repository root, making it trivial to bootstrap ignore rules for new projects. Whether you need to ignore Python's `__pycache__` directories or Rust's `target/` folder, these templates provide battle-tested patterns maintained by the community. ## Repository Structure and File Organization The github/gitignore repository follows a flat file structure where each supported technology receives its own dedicated template. According to the [`README.md`](https://github.com/github/gitignore/blob/main/README.md), the collection separates concerns between language-specific rules and universal development environment configurations. ### Root-Level Language Templates The repository root contains one `.gitignore` file for every mainstream language or platform (e.g., `Python.gitignore`, `Go.gitignore`, `Java.gitignore`). These files represent the language-specific templates referenced in the repository's folder structure documentation. Each file contains patterns targeting compiled artifacts, dependency directories, and tool-specific caches relevant to that particular ecosystem. ### Global and Community Directories Beyond language-specific files, the `Global/` directory houses templates for editors, operating systems, and CI tools that apply across all projects. The `community/` subdirectory contains specialized or version-specific templates for niche frameworks that don't qualify for root-level placement. When configuring your development environment, you typically combine a root-level language template with selections from `Global/` to cover both project artifacts and editor debris. ## How to Use Existing Language-Specific .gitignore Templates Implementing a template requires copying the relevant file from the github/gitignore repository into your project's working directory. You can download files manually or automate the process via command-line tools. To pull a template directly into a new project: ```bash # Initialize a fresh repository git init my-project cd my-project # Download the Go template (replace Go with any language) curl -L https://raw.githubusercontent.com/github/gitignore/main/Go.gitignore -o .gitignore # Verify the contents cat .gitignore ``` After downloading, commit the file to version control like any other source file: ```bash git add .gitignore git commit -m "Add Go .gitignore template from github/gitignore" ``` ## Creating New Language-Specific Templates If your language or framework lacks coverage, you can contribute new templates following the conventions established in [`CONTRIBUTING.md`](https://github.com/github/gitignore/blob/main/CONTRIBUTING.md). The repository maintains strict standards to ensure consistency across the collection. First, create a new file in the repository root named `.gitignore` using capitalized naming without spaces. Refer to existing templates like `Python.gitignore` for structural guidance. Your file should include commented sections organizing patterns by category: ```gitignore # Example skeleton for a fictional language "Foo" # Build artifacts *.fooobj *.foobar # Dependency folder foo_modules/ # IDE files .vscode/ ``` Each template requires a header comment explaining its purpose and optionally referencing official documentation. Once populated, submit your contribution via pull request after forking the repository. Maintainers verify that new templates adhere to naming conventions and documentation requirements specified in [`CONTRIBUTING.md`](https://github.com/github/gitignore/blob/main/CONTRIBUTING.md). ## Configuring Global .gitignore with Language Templates For rules that should apply to every repository on your machine, combine language-specific patterns with global ignore configurations. Git references the global ignore file through the `core.excludesFile` configuration, typically located at `~/.config/git/ignore`. To append a language template to your global configuration: ```bash # Ensure Git recognizes the global ignore file git config --global core.excludesFile ~/.config/git/ignore # Append Python ignores globally curl -L https://raw.githubusercontent.com/github/gitignore/main/Python.gitignore >> ~/.config/git/ignore ``` You can layer global and project-specific ignores for comprehensive coverage. For example, configure global rules for JetBrains IDEs while maintaining project-level language specifics: ```bash # Global ignore file (once per machine) git config --global core.excludesFile ~/.config/git/ignore cat <> ~/.config/git/ignore # Global VS Code ignores *.code-workspace .vscode/ EOF # Project-specific ignore for Rust curl -L https://raw.githubusercontent.com/github/gitignore/main/Rust.gitignore -o .gitignore ``` ## Summary - The github/gitignore repository organizes language-specific .gitignore templates as individual files in the root directory, with each language following the `.gitignore` naming convention. - Copy templates directly using `curl` or manual download, then commit the resulting `.gitignore` file to your project's version control. - Combine root-level language templates with `Global/` directory files to handle both project artifacts and universal editor or OS generated files. - Contribute new templates by creating capitalized files in the repository root, following the style guidelines in [`CONTRIBUTING.md`](https://github.com/github/gitignore/blob/main/CONTRIBUTING.md) and `Python.gitignore`. - Append language patterns to `~/.config/git/ignore` and set `core.excludesFile` for machine-wide ignore rules that persist across all repositories. ## Frequently Asked Questions ### How do I apply a Python .gitignore template to my existing project? Download the `Python.gitignore` file from the github/gitignore repository root using `curl -L https://raw.githubusercontent.com/github/gitignore/main/Python.gitignore -o .gitignore`, then stage and commit the file. If your project already contains a `.gitignore`, merge the contents manually or back up your existing file before overwriting. ### Can I combine multiple language-specific .gitignore templates in one project? Yes. Polyglot projects can concatenate multiple root-level templates into a single `.gitignore` file, or maintain separate ignore files referenced via `.gitignore` includes. For example, a full-stack application might combine `Node.gitignore` and `Python.gitignore` contents to cover both JavaScript and Python artifacts in one repository. ### Where should I place a new language template when contributing to github/gitignore? Place new language-specific templates directly in the repository root using the `.gitignore` naming format with proper capitalization and no spaces. The [`CONTRIBUTING.md`](https://github.com/github/gitignore/blob/main/CONTRIBUTING.md) file specifies that specialized or version-specific frameworks belong in the `community/` directory rather than the root. ### What is the difference between root-level templates and the Global/ directory? Root-level templates like `Go.gitignore` target language-specific build artifacts and dependencies, while `Global/` contains editor, operating system, and tool configurations that apply universally across all projects. You should use root-level files for project repositories and `Global/` files for your machine's global gitignore configuration.