From 5b3d8dc8740493ca0e08b875b42053032dcf460c Mon Sep 17 00:00:00 2001 From: Jonathan Reinink Date: Thu, 21 Mar 2013 09:55:13 -0300 Subject: [PATCH] Update should-i-commit-the-dependencies-in-my-vendor-directory.md MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Tweak option #3 for including dependencies in a GIT repo. --- ...ould-i-commit-the-dependencies-in-my-vendor-directory.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) 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 179ce035f..c2c5d9ba3 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 @@ -24,6 +24,6 @@ If you really feel like you must do this, you have three options: 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. -3. Add a .gitignore rule (`vendor/.git`) to ignore all the vendor .git folders. - This approach does not require to you delete dependencies from disk prior to - running composer update. +3. Add a .gitignore rule (`vendor/.git`) to ignore all the vendor `.git` folders. + This approach does not require that you delete dependencies from disk prior to + running a composer update.