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
Consolidate publish workflows into one #3026
Consolidate publish workflows into one #3026
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems there is currently no way to specify a multi-option input to a manually run workflow. A necessary evil of avoiding to code duplication is to remember the way to invoke this but cargo release
would probably give good enough errors.
Yes, it's the cargo error message if invalid name is passed. I thought of adding a step to validate the input but doing it in bash seemed unnecessarily complex, especially since cargo was going to take care of it anyway |
Nevermind, it was GH app acting up |
* Consolidate publish-* workflows into one * Update workflow name
* Consolidate publish-* workflows into one * Update workflow name
* Consolidate publish-* workflows into one * Update workflow name
Description
Consolidate publish-* workflows into one
This new workflow will be invoked in the same way, except it also takes a space separated list of packages to publish. This change will also guard against any issues that may come up because of running
cargo release
many timesChecklist