-
Notifications
You must be signed in to change notification settings - Fork 112
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
Pre-release hook in CLI options #741
Comments
You can workaround this by writing a For a CLI design, I see this either working as Since before my involvement, we expose most settings. In some other tools. I've adopted a different approach where the expectation is that things that shouldn't change from run-to-run should all be in a config. I'm somewhat tempted to take that approach here. I know your Action replaces the config but, with a workaround, I'm less feeling the need. This isn't a "no" but "I'm hesitant". |
Thanks for the reply. Instead of replacing the configuration, I aim to execute an additional hook on the project before the release.. |
Hi!, thanks for this great tool.
I'm writing a GitHub action to help publish my projects to crates.io. I want to configure the pre-release hook in the CLI options, so I don't need to configure
release.toml
for each project.It's there a way to do this? If not, what do you think about adding this feature?
The text was updated successfully, but these errors were encountered: