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
Maybe it would be nice to have such functionality that standard git merge commit messages are accepted by conventional-pre-commit as they are. By that I mean that they don't need to have "feat: " or the other prefixes. I think that would be good to add them as an exception to the validation rule. Below I'm placing example of such kind of message.
Example: commit message "Merge branch 'main' into feature/name-of-a-feature-branch".
The text was updated successfully, but these errors were encountered:
This has been discussed at length before, see: #19, #39, #76, #84.
TLDR; we are all about enforcing Conventional Commits formatting here. There are plenty of workarounds / alternate tools if you'd like to avoid this checking in certain scenarios.
Hi,
Maybe it would be nice to have such functionality that standard git merge commit messages are accepted by conventional-pre-commit as they are. By that I mean that they don't need to have "feat: " or the other prefixes. I think that would be good to add them as an exception to the validation rule. Below I'm placing example of such kind of message.
Example: commit message "Merge branch 'main' into feature/name-of-a-feature-branch".
The text was updated successfully, but these errors were encountered: