From c6ae3caf5242cdc49d8fc277f39feb4dc3be4b2f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?W=C5=82odzimierz=20Gajda?= Date: Thu, 8 Nov 2012 16:50:05 +0100 Subject: [PATCH] Editorial fix --- doc/02-libraries.md | 2 +- .../should-i-commit-the-dependencies-in-my-vendor-directory.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/02-libraries.md b/doc/02-libraries.md index ee98b3ff7..4e41afab6 100644 --- a/doc/02-libraries.md +++ b/doc/02-libraries.md @@ -117,7 +117,7 @@ the `.gitignore`. ## Light-weight distribution packages -Including the tests and other useless information like .travis.yml in +Including the tests and other useless information like `.travis.yml` in distributed packages is not a good idea. The `.gitattributes` file is a git specific file like `.gitignore` also living diff --git a/doc/faqs/should-i-commit-the-dependencies-in-my-vendor-directory.md b/doc/faqs/should-i-commit-the-dependencies-in-my-vendor-directory.md index 4655d5901..8d4e63af2 100644 --- a/doc/faqs/should-i-commit-the-dependencies-in-my-vendor-directory.md +++ b/doc/faqs/should-i-commit-the-dependencies-in-my-vendor-directory.md @@ -20,7 +20,7 @@ If you really feel like you must do this, you have two options: - Limit yourself to installing tagged releases (no dev versions), so that you only get zipped installs, and avoid problems with the git "submodules". -- Remove the .git directory of every dependency after the installation, then +- Remove the `.git` directory of every dependency after the installation, then you can add them to your git repo. You can do that with `rm -rf vendor/**/.git` but this means you will have to delete those dependencies from disk before running composer update. \ No newline at end of file