Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

question: can MSR define plugin's default options ? #110

Open
Badisi opened this issue Apr 15, 2022 · 0 comments
Open

question: can MSR define plugin's default options ? #110

Badisi opened this issue Apr 15, 2022 · 0 comments

Comments

@Badisi
Copy link
Contributor

Badisi commented 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:

🎉 This PR is included in version 2.0.0-beta.11 🎉

The release is available on npm package (@beta dist-tag)

Your semantic-release bot 📦🚀

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!

@Badisi Badisi changed the title question: can MSR defines plugin's default options ? question: can MSR define plugin's default options ? Apr 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant