Repository files navigation

This is Gitote’s collection of.gitignore file templates.We use this list to populate the.gitignore template choosers availablein the Gitote.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:

• TheIgnoring Files chapter of thePro Git book.
• TheIgnoring Files article on the Gitote Help site.
• Thegitignore(5) manual page.

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

• Provide a link to the application or project’s homepage. Unless it’sextremely popular, there’s a chance the maintainers don’t know about or usethe 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 canto explain what the files being ignored are for.

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

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

• Please only modifyone template per merge request. This helps keep mergerequests 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.

If a template is mostly a list of files installed by a particular version ofsome software (e.g. a PHP framework) then it's brittle and probably no morehelpful than a simplels. If it's not possible to curate a small set ofuseful rules, then the template might not be a good fit for this collection.

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

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 merge request from your fork’s branch to ourmaster branch.

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

MIT.