You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In our GitLab Pipeline the plugin breaks a composer install, because no git directory exists. Would it be possible to skip the installation of the hooks in this case? Maybe using a CI/CD variable?
CaptainHook Composer Plugin
Installation failed, reverting ./composer.json to its original content.
In ComposerPlugin.php line 274:
Shiver me timbers! CaptainHook could not install yer git hooks! (git directory not found)
The text was updated successfully, but these errors were encountered:
@sebastianfeldmann: Would checking for an existing .git folder be something that The Cap'n should do? Or would we skip installing The Ca'n in the first place when no .git folder is found?
Or should we check for the usual suspects like CI-environment variables to not install The Cap'n in the first place? That might make more sense perhaps...
In our GitLab Pipeline the plugin breaks a
composer install
, because no git directory exists. Would it be possible to skip the installation of the hooks in this case? Maybe using a CI/CD variable?The text was updated successfully, but these errors were encountered: