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
For me, I'm trying to use the single command git commit and it prompt to choose my type:
husky > pre-commit (node v12.17.0)
ℹ No staged files match any configured task.
husky > prepare-commit-msg (node v12.17.0)
? Select the type of change that you're committing: (Use arrow keys or type to search)
❯ test: Adding missing tests
feat: A new feature
fix: A bug fix
chore: Build process or auxiliary tool changes
docs: Documentation only changes
refactor: A code change that neither fixes a bug or adds a feature
style: Markup, white-space, formatting, missing semi-colons...
Then I make de description:
...
? Select the type of change that you're committing: chore: Build process or auxiliary tool changes
? Write a short, imperative mood description of the change:
[-------------------------------------------------------------] 34 chars left
chore: husky hook on git-cz
But it's falling back to VIM to edit COMMIT_EDITMSG:
For me, I'm trying to use the single command
git commit
and it prompt to choose my type:Then I make de description:
But it's falling back to VIM to edit COMMIT_EDITMSG:
My pakcage.json husky config and version:
-> Some can help me with this issue? There is some "thing" to avoid open the
COMMIT_EDITMSG
or is the default behavior?Originally posted by @jaikme in #688 (comment)
The text was updated successfully, but these errors were encountered: