-
Notifications
You must be signed in to change notification settings - Fork 930
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Add whitespace handling (trim) for commit messages #3199
Comments
You mean if it's intended not to trim inputs? tbh I don't know. What would you expect? Is this blocking you in a way? Creating a commit message I usually use |
I expect it to not count leading whitespaces. Yes, it is super blocking in case of mistakes. |
Do you have time and motivation to look into this? |
So you want to allow leading whitespace? IMO, that's an invalid commit message and is being linted correctly - albeit with a misleading error message. The purpose of commitlint is to throw errors when you make mistakes - so blocking is the correct behaviour. No? |
True, I can understand this as well |
Currently when having a leading space, the error message says that the subject is empty. |
The text was updated successfully, but these errors were encountered: