3932f1f0ce
Libraries/Projects using [Composer](http://getcomposer.org) for dependency management should include a `.gitignore` file like this. It ignores the vendor folder which Composer uses for dependencies, classmaps and others. Composer keeps git repositories in this folder so it is cleaner if it is ignored. [`composer.lock` should not be ignored.](http://getcomposer.org/doc/01-basic-usage.md#composer-lock-the-lock-file) > Commit your application's composer.lock (along with composer.json) into version control. > For your library you may commit the composer.lock file if you want to. This can help your team to always test against the same dependency versions. However, this lock file will not have any effect on other projects that depend on it. It only has an effect on the main project.
A Collection of Useful .gitignore Templates
That's what we're trying to build. Please contribute by forking and sending a pull request.
Also please only modify one file per commit. This'll make merging easier for everyone.
Global gitignores (OS-specific, editor-specific) should go into the
Global/ directory.
For more information on gitignore: gitignore(5)
Pull Requests
Since this repo includes a large and diverse number of programming languages, frameworks, editors, and ecosystems, it's very helpful if you can provide a link to information supporting your pull request. Up-to-date, canonical documentation that mentions the files to be ignored is best.
This ensures we can efficiently go through pull requests and keep quality high.
Global Ignores
git has a global configuration that applies rules to all of your projects. For example:
git config --global core.excludesfile ~/.global_ignore
... will apply the rules in ~/.global_ignore for all of your repos.
This is useful if you use an editor (like Emacs) that drops backup files, or if you work in an environment that generates binary or intermediate files that are always ignored.