Do not prevent Git usage if Captain Hook installation is broken about captainhook

[Wirone]

I started implementing this with something like this:

diff --git a/src/Hook/Template/Local/Shell.php b/src/Hook/Template/Local/Shell.php
index 006002e4..d7ce30fb 100644
--- a/src/Hook/Template/Local/Shell.php
+++ b/src/Hook/Template/Local/Shell.php
@@ -91,11 +91,15 @@ class Shell extends Template\Local
             $useTTY,
             [
                 '',
-                $executable
+                'if [ -f "' . $executable . '" ] ; then',
+                '    ' . $executable
                     . ' $INTERACTIVE'
                     . ' --configuration=' . $this->configPath
                     . ' --bootstrap=' . $this->bootstrap
                     . ' hook:' . $hook . ' "$@"' . $useStdIn,
+                'else',
+                '    echo "Captain Hook is not installed, run \`composer install\`!";',
+                'fi',
             ]
         );
     }

But it handles only scenario with missing vendor/bin/captainhook. The second one is harder, I don't actually know where I should hook into 🙂

[sebastianfeldmann]

If they delete the vendor folder they can also remove the hook scripts.

My advice, use the PHAR version install it with phive and keep your dev tooling out of Composer :)

[Wirone]

Yes, they can, but I'm talking about people not necessarily knowing about tooling behind the process. In such cases those people are clueless, they get error and ask about it on Slack 🙂. I believe it could be supported, but understand if you don't want it (but then it shouldn't be closed as "completed" 😝).