gitignore/Composer.gitignore

composer.phar
/vendor/

# Commit your application's lock file https://getcomposer.org/doc/01-basic-usage.md#commit-your-composer-lock-file-to-version-control
# You may choose to ignore a library lock file http://getcomposer.org/doc/02-libraries.md#lock-file
# composer.lock
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. 2013-08-19 10:38:52 -04:00			`composer.phar`
Incorrect Dir Path When generating the ignore rules for Composer, an incorrect format is used. The vendor directory added is written `vendor/`, which causes other `vendors` directories to be ignored. The correct format to use is `/vendor/`, which would only ignore the root `vendor` directory. 2015-11-29 23:03:09 -05:00			`/vendor/`
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. 2013-08-19 10:38:52 -04:00
Fix link to go to current anchor 2017-10-27 18:55:29 -04:00			`# Commit your application's lock file https://getcomposer.org/doc/01-basic-usage.md#commit-your-composer-lock-file-to-version-control`
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. 2013-08-19 10:38:52 -04:00			`# You may choose to ignore a library lock file http://getcomposer.org/doc/02-libraries.md#lock-file`
Fix eol issues Some files don't contain a line separator ('\n') at the end. Add the missing eol. In POSIX, all lines of text should end with a newline character by definition. See http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap03.html section 3.397 for more. See https://gist.github.com/jacknagel/1020172 for a gist of the issue. 2014-04-23 16:50:28 -04:00			`# composer.lock`