search

greenkeeperio / greenkeeper-lockfile

:lock: Your lockfile, up to date, all the time
https://greenkeeper.io
183 stars 73 forks source link

Commit with --no-verify #75

Open mightyiam opened 6 years ago

mightyiam commented 6 years ago

Woops. It seems that my commit hook is running in CI when greenkeeper-lockfile-update makes the commit. See here. And by the way, ignore the warnings there—they're a different issue. Perhaps we should commit with --no-verify?

travi commented 6 years ago

i'm curious what you are using to manage your hooks. personally, i use husky, which specifically checks to see if it is running in a CI environment and does not install the hooks.

rather than greenkeeper-lockfile (which should only run on CI) needing to change to support hooks, it seems like it would be better to prevent the hooks from being in place on CI.

thoughts?