Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
A collection of useful .gitignore templates
branch: master

This branch is even with github:master

Fetching latest commit…

Cannot retrieve the latest commit at this time

Failed to load latest commit information.
Global
Actionscript.gitignore
Ada.gitignore
Agda.gitignore
Android.gitignore
AppEngine.gitignore
AppceleratorTitanium.gitignore
ArchLinuxPackages.gitignore
Autotools.gitignore
C++.gitignore
C.gitignore
CFWheels.gitignore
CMake.gitignore
CONTRIBUTING.md
CUDA.gitignore
CakePHP.gitignore
ChefCookbook.gitignore
Clojure.gitignore
CodeIgniter.gitignore
CommonLisp.gitignore
Composer.gitignore
Concrete5.gitignore
Coq.gitignore
CraftCMS.gitignore
DM.gitignore
Dart.gitignore
Delphi.gitignore
Drupal.gitignore
EPiServer.gitignore
Eagle.gitignore
Elisp.gitignore
Elixir.gitignore
Erlang.gitignore
ExpressionEngine.gitignore
ExtJs.gitignore
Fancy.gitignore
Finale.gitignore
ForceDotCom.gitignore
Fortran.gitignore
FuelPHP.gitignore
GWT.gitignore
Gcov.gitignore
GitBook.gitignore
Go.gitignore
Gradle.gitignore
Grails.gitignore
Haskell.gitignore
IGORPro.gitignore
Idris.gitignore
Java.gitignore
Jboss.gitignore
Jekyll.gitignore
Joomla.gitignore
Jython.gitignore
KiCAD.gitignore
Kohana.gitignore
LICENSE
LabVIEW.gitignore
Laravel.gitignore
Leiningen.gitignore
LemonStand.gitignore
Lilypond.gitignore
Lithium.gitignore
Lua.gitignore
Magento.gitignore
Maven.gitignore
Mercury.gitignore
MetaProgrammingSystem.gitignore
Meteor.gitignore
Nanoc.gitignore
Nim.gitignore
Node.gitignore
OCaml.gitignore
Objective-C.gitignore
Opa.gitignore
OpenCart.gitignore
OracleForms.gitignore
Packer.gitignore
Perl.gitignore
Phalcon.gitignore
PlayFramework.gitignore
Plone.gitignore
Prestashop.gitignore
Processing.gitignore
Python.gitignore
Qooxdoo.gitignore
Qt.gitignore
R.gitignore
README.md
ROS.gitignore
Rails.gitignore
RhodesRhomobile.gitignore
Ruby.gitignore
Rust.gitignore
SCons.gitignore
Sass.gitignore
Scala.gitignore
Scrivener.gitignore
Sdcc.gitignore
SeamGen.gitignore
SketchUp.gitignore
Stella.gitignore
SugarCRM.gitignore
Swift.gitignore
Symfony.gitignore
SymphonyCMS.gitignore
TeX.gitignore
Textpattern.gitignore
TurboGears2.gitignore
Typo3.gitignore
Umbraco.gitignore
Unity.gitignore
VVVV.gitignore
VisualStudio.gitignore
Waf.gitignore
WordPress.gitignore
Xojo.gitignore
Yeoman.gitignore
Yii.gitignore
ZendFramework.gitignore
Zephir.gitignore

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.