public-mirrors
/
composer
mirror of https://github.com/composer/composer
1
0
Fork 0
Code

Merge pull request #9174 from IvanZugec/patch-1 

Capitalised the word "But" in point 3.
pull/9179/head
Jordi Boggiano 2020-09-02 08:54:15 +02:00 committed by GitHub
parent 4ac9f44571 2b4e9742c4
commit 86ff43d8b9
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/faqs/should-i-commit-the-dependencies-in-my-vendor-directory.md
View File

@ -25,7 +25,7 @@ If you really feel like you must do this, you have a few options:
3. Remove the `.git` directory of every dependency after the installation, then 3. 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` you can add them to your git repo. You can do that with `rm -rf vendor/**/.git`
in ZSH or `find vendor/ -type d -name ".git" -exec rm -rf {} \;` in Bash. in ZSH or `find vendor/ -type d -name ".git" -exec rm -rf {} \;` in Bash.
but this means you will have to delete those dependencies from disk before But this means you will have to delete those dependencies from disk before
running composer update. running composer update.
4. Add a .gitignore rule (`/vendor/**/.git`) to ignore all the vendor `.git` folders. 4. 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 This approach does not require that you delete dependencies from disk prior to