Right now when the publishing CI flow is done it will try to run git push to publish the new git tags but this triggers the on-push git hook that we use via Husky. Example: https://github.com/twilio-labs/serverless-toolkit/actions/runs/3953164384/jobs/6769250287
We should disable this in CI. Normally you do this by running --no-verify with git push but since git push is done by the changeset CLI we don't have direct control.
One option might be to add HUSKY=0 as environment variable to the publish step which should disable this behavior as well. https://typicode.github.io/husky/#/?id=bypass-hooks
Right now when the publishing CI flow is done it will try to run
git pushto publish the new git tags but this triggers the on-push git hook that we use via Husky. Example: https://github.com/twilio-labs/serverless-toolkit/actions/runs/3953164384/jobs/6769250287We should disable this in CI. Normally you do this by running
--no-verifywithgit pushbut sincegit pushis done by thechangesetCLI we don't have direct control.One option might be to add
HUSKY=0as environment variable to the publish step which should disable this behavior as well. https://typicode.github.io/husky/#/?id=bypass-hooks