-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Support "multi-choice" input type for manual workflows #2076
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
Comments
I run into the same problem. We want to select multiple schemes to build for our iOS App but we have way more than 10 schemes. It would be definitely a helpful feature. Otherwise, you have to work with the string input type, which can lead to input errors. |
+1 |
10 similar comments
+1 |
+1 |
+1 |
+1 |
+1 |
+1 |
+1 |
+1 |
+1 |
+1 |
I would be really great feature to have since many use cases are there. |
+1 |
3 similar comments
+1 |
+1 |
+1 |
+1 |
+1 |
10 similar comments
+1 |
+1 |
+1 |
+1 |
+1 |
+1 |
+1 |
+1 |
+1 |
+1 |
+1 |
7 similar comments
+1 |
👍🏻 |
+1 |
+1 |
+1 |
+1 |
+1 |
+10 |
+1 |
7 similar comments
+1 |
+1 |
+1 |
+1 |
+1 |
+1 |
+1 |
|
+1 |
+100 |
+1 |
3 similar comments
+1 |
+1 |
+1 |
+100 |
+1 |
2 similar comments
+1 |
+1 |
Describe the enhancement
Current set of input types doesn't cover some use-cases for manual workflows
We use a single gh-action as an entrypoint of deploying packages from our monorepo, and sometimes we need to manually deploy several packages simultaneously. Up until now we just went with a set of Booleans, so we could tick all the packages we needed to run our CI/CD against via UI. However, we speedily reached a limit of 10 input values
Introducing an input type that would store a, say, json array could help:
...and in fact would be more logical with less copy-paste overhead for our use-case
The text was updated successfully, but these errors were encountered: