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
I found that the combination of commit type (fix, feat, etc) + scope + commit header can easily reach the < 50 character limit that's recommended not only when viewing a commit in Github, but also here:
gacp has implemented the commitlintrules about max-lengths since 2.6.1. If a user inputs a commit section (one of header, body, or footer) longer than the commitlintconfig requires, the commit message will be trimmed when performing git commit.
You can try to add a commitlint config to trim the commit message.
2. Prevent or warn when a user is typing.
I think this is better than 1.
Maybe we can look into the terminal prompt API to see whether it works that way.
I found that the combination of commit type (fix, feat, etc) + scope + commit header can easily reach the < 50 character limit that's recommended not only when viewing a commit in Github, but also here:
https://chris.beams.io/posts/git-commit/
This is a request to prevent or warn the user when their commit title is > 50 characters.
The text was updated successfully, but these errors were encountered: