Skip to content
A collection of useful .gitignore templates
Find file
Pull request Compare This branch is 10 commits ahead, 412 commits behind master.
Latest commit 765ecc3 @shiftkey shiftkey some more annotation
Failed to load latest commit information.
Global
Actionscript.gitignore ensure single trailing newline
Ada.gitignore
Agda.gitignore
Android.gitignore
AppEngine.gitignore
AppceleratorTitanium.gitignore Added Appcelerator Titanium .gitignore file.
ArchLinuxPackages.gitignore Add .jar, .exe and .msi
Autotools.gitignore
C++.gitignore
C.gitignore
CFWheels.gitignore add cfwheels gitignore
CMake.gitignore Added a .gitignore for files auto-generated by the CMake build-system.
CONTRIBUTING.md
CUDA.gitignore
CakePHP.gitignore comment out CakePHP version headers
ChefCookbook.gitignore
Clojure.gitignore
CodeIgniter.gitignore Fixed CodeIgniter.gitignore
CommonLisp.gitignore
Composer.gitignore
Concrete5.gitignore ensure single trailing newline
Coq.gitignore
CraftCMS.gitignore
DM.gitignore ensure single trailing newline
Dart.gitignore
Delphi.gitignore
Drupal.gitignore Fixes uncomplete CTools
EPiServer.gitignore ensure single trailing newline
Eagle.gitignore .gitignore file for Eagle
Elisp.gitignore
Elixir.gitignore
Erlang.gitignore Add ebin, rel example, concrete dev mode, .rebar
ExpressionEngine.gitignore Merge pull request #488 from nanadevelopment/eeConfigAdd
ExtJs.gitignore
Fancy.gitignore
Finale.gitignore
ForceDotCom.gitignore ensure single trailing newline
Fortran.gitignore
FuelPHP.gitignore
GWT.gitignore
Gcov.gitignore
GitBook.gitignore Correct URL for NPM URL reference
Go.gitignore
Gradle.gitignore Avoid ignoring Gradle wrapper jar file
Grails.gitignore
Haskell.gitignore
IGORPro.gitignore
Idris.gitignore Add an Idris gitignore
Java.gitignore
Jboss.gitignore
Jekyll.gitignore
Joomla.gitignore Update Joomla.gitignore
KiCAD.gitignore
Kohana.gitignore
LICENSE
LabVIEW.gitignore
Laravel.gitignore Add ".env" to Laravel.gitignore
Leiningen.gitignore
LemonStand.gitignore
Lilypond.gitignore
Lithium.gitignore The Lithium app should be the root repo folder
Lua.gitignore
Magento.gitignore
Maven.gitignore
Mercury.gitignore
MetaProgrammingSystem.gitignore Grammar/formatting tweak to comments
Nanoc.gitignore Capitalise initial letter in template filenames for consistency/sorting
Nim.gitignore Create Nim.gitignore
Node.gitignore
OCaml.gitignore
Objective-C.gitignore
Opa.gitignore Added Opa.gitignore
OpenCart.gitignore Returned lost config file
OracleForms.gitignore
Packer.gitignore Add a support for packer
Perl.gitignore
Phalcon.gitignore
PlayFramework.gitignore
Plone.gitignore
Prestashop.gitignore
Processing.gitignore Added the processing project
Python.gitignore
Qooxdoo.gitignore
Qt.gitignore
R.gitignore
README.md
ROS.gitignore
Rails.gitignore
RhodesRhomobile.gitignore Add Rhodes mobile application framework gitignore
Ruby.gitignore
Rust.gitignore revert
SCons.gitignore Added SCons.gitignore
Sass.gitignore
Scala.gitignore Ignore .history files
Scrivener.gitignore
Sdcc.gitignore
SeamGen.gitignore
SketchUp.gitignore
Stella.gitignore Capitalise initial letter in template filenames for consistency/sorting
SugarCRM.gitignore Explanations for ignoring the cache directory
Swift.gitignore
Symfony.gitignore Add 'build' directory
SymphonyCMS.gitignore
TeX.gitignore
Textpattern.gitignore
TurboGears2.gitignore
Typo3.gitignore
Umbraco.gitignore
Unity.gitignore Made it so the folders only get ingored in the root
VVVV.gitignore ensure single trailing newline
VisualStudio.gitignore
Waf.gitignore
WordPress.gitignore
Xojo.gitignore
Yeoman.gitignore
Yii.gitignore
ZendFramework.gitignore
Zephir.gitignore Added comments for Zephir

README.md

A collection of .gitignore templates

This is GitHub’s collection of .gitignore file templates. We use this list to populate the .gitignore template choosers available in the GitHub.com interface when creating new repositories and files.

For more information about how .gitignore files work, and how to use them, the following resources are a great place to start:

Folder structure

The files in the root directory are for .gitignore templates that are project specific, such as language or framework specific templates. Global (operating system or editor specific) templates should go into the Global/ directory.

Contributing guidelines

We’d love you to help us improve this project. To help us keep this collection high quality, we request that contributions adhere to the following guidelines.

  • Provide a link to the application or project’s homepage. Unless it’s extremely popular, there’s a chance the maintainers don’t know about or use the language, framework, editor, app, or project your change applies to.

  • Provide links to documentation supporting the change you’re making. Current, canonical documentation mentioning the files being ignored is best. If documentation isn’t available to support your change, do the best you can to explain what the files being ignored are for.

  • Explain why you’re making a change. Even if it seems self-evident, please take a sentence or two to tell us why your change or addition should happen. It’s especially helpful to articulate why this change applies to everyone who works with the applicable technology, rather than just you or your team.

  • Please consider the scope of your change. If your change specific to a certain language or framework, then make sure the change is made to the template for that language or framework, rather than to the template for an editor, tool, or operating system.

  • Please only modify one template per pull request. This helps keep pull requests and feedback focused on a specific project or technology.

In general, the more you can do to help us understand the change you’re making, the more likely we’ll be to accept your contribution quickly.

Please also understand that we can’t list every tool that ever existed. Our aim is to curate a collection of the most common and helpful templates, not to make sure we cover every project possible. If we choose not to include your language, tool, or project, it’s not because it’s not awesome.

Contributing workflow

Here’s how we suggest you go about proposing a change to this project:

  1. Fork this project to your account.
  2. Create a branch for the change you intend to make.
  3. Make your changes to your fork.
  4. Send a pull request from your fork’s branch to our master branch.

Using the web-based interface to make changes is fine too, and will help you by automatically forking the project and prompting to send a pull request too.

License

MIT.

Something went wrong with that request. Please try again.