1
0
Commit Graph

4 Commits

Author SHA1 Message Date
Clifford
ca57c447a3
Fix link to go to current anchor 2017-10-27 17:55:29 -05:00
Julien Liabeuf
5bb4e85357 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-30 11:03:09 +07:00
Jacob Rigby
5eacf05adb 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:02:01 -05:00
Haralan Dobrev
3932f1f0ce 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-11-09 13:38:32 +02:00