-
Notifications
You must be signed in to change notification settings - Fork 4
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
Add an ability to configure plugins #228
Comments
I do not want the changelog file from getting created. |
The whole point of this project is to have a Github action around semantic-release plugin. |
I guess the ask is to still be able to release (push packages, tag, ...) but do not generate a changelog. So basically, if you look at our Readme, do "optionally, updates the CHANGELOG.md file based on the analyzed commits" instead of "updates the CHANGELOG.md file based on the analyzed commits". |
@mad-it I would want to have the releases but i do not want to create changelog file, this interferes if i am not using trunk-based rather use a two-branch model with master and next(prerelease barnch). I constant willl have to rebase changes from the master because of changelog updates. |
+1 to @samof76 's concern and +1 to @merlinnot 's explanation I'd want to use this github action for doing production releases in some Additionally, I don't want the bot polluting my commit history. From what I've tested so far, it seems that the version of release is dependent on the bot's last commit (cmiiw, not sure about this one). Can we please make this optional? i.e maybe we can depend on existing tag instead? cc: @mad-it |
Hi! I have an updated on this one: we'll be working on a functionality to fully customize plugins, which will enable both disabling default and enabling additional plugins. While we can't commit to any specific date, we hope to get to it by the end of the year. |
@cadaroya I have added a PR that removes allows for disabling generating or updating a CHANGELOG.md file, but even so, the action still commits several files by default if used with the I'm trying to grasp your exact use case, so that we may adequately improve the action's behaviour. Can you elaborate a bit on:
Thank you! |
Disabling CHANGELOG.md generation was merged as a mitigation to this issues described here. Further on, I am moving to enable configuring all plugins directly by passing a configuration file to the action. |
How do i disable sematic-release plugins?
The text was updated successfully, but these errors were encountered: