浏览代码

update documentation to work for ZSH or Bash

Richard K Miller 11 年之前
父节点
当前提交
1ee0f28e79
共有 1 个文件被更改,包括 2 次插入1 次删除
  1. 2 1
      doc/faqs/should-i-commit-the-dependencies-in-my-vendor-directory.md

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

@@ -23,7 +23,8 @@ If you really feel like you must do this, you have a few options:
 2. Use --prefer-dist or set `preferred-install` to `dist` in your
 2. Use --prefer-dist or set `preferred-install` to `dist` in your
    [config](../04-schema.md#config).
    [config](../04-schema.md#config).
 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.
    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.