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
But when releasing multiple packages it is obvious that the version here (ie. 2.0.0-beta.11) does not really help.
One could use the plugin's successComment option to change the comment and maybe use something like nextRelease.gitTag instead of nextRelease.version (see get-success-comment.js#L7).
But I was wondering if MSR could set that by default ? and how ? as I'm not familiar with how SR/MSR lifecycle hooks are working.
Thanks!
The text was updated successfully, but these errors were encountered:
Badisi
changed the title
question: can MSR defines plugin's default options ?
question: can MSR define plugin's default options ?
Apr 15, 2022
When using the plugin
@semantic-release/github
, the following comment is added to any issues or PRs that relates to the release:But when releasing multiple packages it is obvious that the version here (ie.
2.0.0-beta.11
) does not really help.One could use the plugin's successComment option to change the comment and maybe use something like
nextRelease.gitTag
instead ofnextRelease.version
(see get-success-comment.js#L7).But I was wondering if MSR could set that by default ? and how ? as I'm not familiar with how SR/MSR lifecycle hooks are working.
Thanks!
The text was updated successfully, but these errors were encountered: