From 3932f1f0ce7a687f3df4ac376aa3561c28dd98c5 Mon Sep 17 00:00:00 2001 From: Haralan Dobrev Date: Mon, 19 Aug 2013 17:38:52 +0300 Subject: [PATCH] Add Composer.gitignore for composer packages 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. --- Composer.gitignore | 6 ++++++ 1 file changed, 6 insertions(+) create mode 100644 Composer.gitignore diff --git a/Composer.gitignore b/Composer.gitignore new file mode 100644 index 00000000..aa5997f4 --- /dev/null +++ b/Composer.gitignore @@ -0,0 +1,6 @@ +composer.phar +vendor/ + +# Commit your application's lock file http://getcomposer.org/doc/01-basic-usage.md#composer-lock-the-lock-file +# You may choose to ignore a library lock file http://getcomposer.org/doc/02-libraries.md#lock-file +# composer.lock \ No newline at end of file -- 2.39.5