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'm wondering if we should actually enforce this for master branch so that all commit messages on master are formatted as conventional commits?
(Note that this would not affect commit messages in PR'd branches as those commits are squashed on merge anyway, meaning only the person merging the PR has to make sure the merged commit is formatted correctly.
Also for verification requests we would use our own tag called verify: or something ^^
The text was updated successfully, but these errors were encountered:
Both @Alystrasz and I have been committing using conventional commit messages, primarily out of habit
I'm wondering if we should actually enforce this for
master
branch so that all commit messages onmaster
are formatted as conventional commits?(Note that this would not affect commit messages in PR'd branches as those commits are squashed on merge anyway, meaning only the person merging the PR has to make sure the merged commit is formatted correctly.
Also for verification requests we would use our own tag called
verify:
or something ^^The text was updated successfully, but these errors were encountered: