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
First, I want to say thanks for this great package 🙏
Description
Adding a custom commit message or a custom commit message prefix would be great. The reason being that many folks who may use this package must adhere to some level of compliance that calls for it. For example, all my commit messages must be prefixed with MY-JIRA-PROJ-NAME-####.
Possible implementation
A config flag that would ask for a message prefix or perhaps an entirely custom commit message.
Alternatives
Ignore this because it's entirely too bespoke.
The text was updated successfully, but these errors were encountered:
Sounds like a interesting and useful change that could be useful across projects.
We are using npm version to update version and this creates the commit as per the npm docs.
The same doc has steps to add if we want a particular commit message in the version commit. We should be able to use this to incorporate a entirely custom commit message.
First, I want to say thanks for this great package 🙏
Description
Adding a custom commit message or a custom commit message prefix would be great. The reason being that many folks who may use this package must adhere to some level of compliance that calls for it. For example, all my commit messages must be prefixed with
MY-JIRA-PROJ-NAME-####
.Possible implementation
A config flag that would ask for a message prefix or perhaps an entirely custom commit message.
Alternatives
Ignore this because it's entirely too bespoke.
The text was updated successfully, but these errors were encountered: