Steps to Reproduce
1. set a type-enum rule
2. try to commit and test the rule then you see the input is coming from the previous commit message
there is also a StackOverflow page related to this:
https://stackoverflow.com/questions/78731073/commitlint-with-husky-failing-due-to-incorrect-commit-message-from-previous-comm
Current Behavior
No response
Expected Behavior
It should use the current commit message
Affected packages
Possible Solution
No response
Context
No response
commitlint --version
@commitlint/cli
git --version
2.45.2
node --version
20.14.0
Steps to Reproduce
Current Behavior
No response
Expected Behavior
It should use the current commit message
Affected packages
Possible Solution
No response
Context
No response
commitlint --version
@commitlint/cli
git --version
2.45.2
node --version
20.14.0