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
It would be nice if I can have the message option set on my .npmrc and commit-and-tag-version could use that if no --releaseCommitMessageFormat was passed in the CLI. That way, if someone releases using npm version for any reason, at least the messages will always be consistent.
The text was updated successfully, but these errors were encountered:
Thanks for this request. I really like this idea - in fact, it would be nice if you could specify any options in any way.
In general, the options need to be overhauled. At the moment, there are some options that are only available via the package.json keys, and some options that are only available via the CLI. At the time that those options are overhauled, it would be very easy to add .npmrc as another potential source (although perhaps .versionrc is a more appropriate place, I am not sure).
It would be nice if I can have the
message
option set on my.npmrc
andcommit-and-tag-version
could use that if no--releaseCommitMessageFormat
was passed in the CLI. That way, if someone releases usingnpm version
for any reason, at least the messages will always be consistent.The text was updated successfully, but these errors were encountered: