-
Notifications
You must be signed in to change notification settings - Fork 19
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
Configure plugin through pluginOptions #47
Comments
Oh wow - is this true (and where is THAT documented?) :) That explains why I have been banging my head against a wall for an hour !! Yes please make it possible to contain the entire configuration in one place! |
Take the example from the file The way options are retrieved is only using the maven-semantic-release/lib/publish.js Lines 10 to 14 in 3a88d61
If you read the semantic-release docs the object I ended up forking the project and completely cleaning it from the conveyal workflow which is a workflow I do not use. |
Reading the docs here : https://github.com/semantic-release/semantic-release/blob/master/docs/usage/plugins.md#plugin-options-configuration It seems that you could put the configuration at the root of your semantic release config file. I remember trying this out, but for some reason, couldn't achieve it. Please tell me if you successfully achieve it. |
The only way to configure the plugin behavior is by passing arguments to the CLI.
I like to work only with a written config and at this moment global flags are only supported through the CLI.
It would be nice to be able to configure them through the json config.
Example:
The text was updated successfully, but these errors were encountered: