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
Its sort similar but a bit of work around as we do not yet have solution for #448
I tried to trigger commitizen in pre-commit stage so it override the actual git commit behavior, but when commitizen ui popped up, pre-commit just ran through it instead of pausing at the commitizen step so I can utilize its UI for commit the change.
Is there way we can config pre-commit not to conclude until the first finished?
Thanks!
The text was updated successfully, but these errors were encountered:
olgn
added a commit
to olgn/cz-cli
that referenced
this issue
Mar 19, 2019
fixes#448 (re #462)
This pr allows project maintainers to enforce Commitizen generated commit messages as part of the workflow triggered by the `git commit` command.
* implements the `--hook` flag, which directs Commitizen to edit the `.git/COMMIT_EDITMSG` file directly.
* documents the use of the `--hook` flag in the `README`, both through traditional `git hooks` and `husky`.
Its sort similar but a bit of work around as we do not yet have solution for #448
I tried to trigger commitizen in pre-commit stage so it override the actual git commit behavior, but when commitizen ui popped up, pre-commit just ran through it instead of pausing at the commitizen step so I can utilize its UI for commit the change.
Is there way we can config pre-commit not to conclude until the first finished?
Thanks!
The text was updated successfully, but these errors were encountered: