NoVerify builder option (or command flag) works only when doing git push.
See original GitHub issueI’ve started using your library a few days ago and I found a use case that you may haven’t considered.
I’m not sure if it’s a good or bad practice, but I have my local testing pipeline (lint, test, etc) on my pre-commit hook.
I followed the path of the options that we defined on the architect target definition, and it seems that the only place where you explicitly use the noVerify option is in here: , line 77.
My condition is: I’ve put the affected --target=version --no-verify command into another hook, after the pre-commit.
My issue is: when the command makes the version changes commit, it runs my pre-commit hook again, disregarding the noVerify option.
I’m not sure if this is a designed behaviour or just a strange use case.
Please, let me know if I can be of any help.
Issue Analytics
- State:
- Created 2 years ago
- Comments:9 (5 by maintainers)

Top Related StackOverflow Question
Hi, finally fixed this. Thanks for reporting!
@gabsmprocha @nicolashernandezamor-drd It’s weird because the underlying package that creates the commit gets the
noVerifyoption correctly. I need to investigate further, but I’m currently working on something else, I’m not against another hand for fixing this.