Replies: 127 comments 37 replies
-
|
That's a neat idea that I hadn't considered. We'll put this on the backlog. Thanks for the feedback, @Suchit8. |
Beta Was this translation helpful? Give feedback.
-
|
Is there a feature request for this? |
Beta Was this translation helpful? Give feedback.
-
|
This (or something like it) is really important to support dynamic environments. It's getting pretty common to spin up environments for a single branch or testing of a release. Esp with microservices it can become a lot of work to update N number of workflow dispatch input choices. While it could be environment variables that would be limiting and in a way bring one back to the same issue. Having to update data somewhere. One thing that might help a lot of users is to support a dynamic environment field in the workflow_dispatch that was dynamically generated from environments declared at the repo level. |
Beta Was this translation helpful? Give feedback.
-
|
It also would be very useful to be able to fill out the options of the dropdown based on the tags of some other repository. |
Beta Was this translation helpful? Give feedback.
-
|
this feature is very needed, in our use case, we just want to have a list of option which is the file name listed from the root, for example make the output of |
Beta Was this translation helpful? Give feedback.
-
|
Hello, |
Beta Was this translation helpful? Give feedback.
-
|
In the meantime, has anyone tried to update the workflow file (its a yaml after all) from another event, committing it to the repo, so when end-user want to use the workflow_dispatch the values are in there. I know it is a bit arsh design but would it work ? |
Beta Was this translation helpful? Give feedback.
-
|
Is there any update on the feature request? As a result, workflow dispatch will be a much more powerful tool |
Beta Was this translation helpful? Give feedback.
-
|
This feature would be super useful for me as well! |
Beta Was this translation helpful? Give feedback.
-
|
+1 |
Beta Was this translation helpful? Give feedback.
-
|
+1 |
Beta Was this translation helpful? Give feedback.
-
|
+1 |
Beta Was this translation helpful? Give feedback.
-
|
+1 (missing this feature, is the only feature I miss after migrate from Jenkins to Github action, will be nice to be added) |
Beta Was this translation helpful? Give feedback.
-
|
+1 |
Beta Was this translation helpful? Give feedback.
-
|
+1 |
Beta Was this translation helpful? Give feedback.
-
|
+1 |
Beta Was this translation helpful? Give feedback.
-
|
+1 |
Beta Was this translation helpful? Give feedback.
-
|
+1 |
Beta Was this translation helpful? Give feedback.
-
|
+1 |
Beta Was this translation helpful? Give feedback.
-
|
+1 |
Beta Was this translation helpful? Give feedback.
-
|
+1 |
Beta Was this translation helpful? Give feedback.
-
|
+1 |
Beta Was this translation helpful? Give feedback.
-
|
+1 |
Beta Was this translation helpful? Give feedback.
-
|
+1 |
Beta Was this translation helpful? Give feedback.
-
|
this would help me SO MUCH IF IT EXISTED. |
Beta Was this translation helpful? Give feedback.
-
|
This feature is really needed to avoid user input errors or typos. Is there at least a recommended workaround? 🤔 |
Beta Was this translation helpful? Give feedback.
-
|
Is this at least being considered for the near future? |
Beta Was this translation helpful? Give feedback.
-
|
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
Beta Was this translation helpful? Give feedback.
-
|
I was just looking into this sort of functionality myself so that I could update our production release workflow. We have an action which only triggers from The latter I could more or less accomplish by just having two inputs, the image tag and a "promote_current_staging" boolean and if the "promote" option is selected, check what is there (or have staging deployments record it somewhere), otherwise use the hand-typed input. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Can we have a feature in the GitHub actions to populate the workflow_dispatch input values dynamically, maybe using some API response or using other GitHub workflow outputs?
Ex: Current workflow
on:
workflow_dispatch:
inputs:
SOURCE_REGION:
type: choice
default:
required: true
options:
- us-west-1
- us-west-2
- us-east-1
- eu-west-1
Ex: Feature looking for-
on:
workflow_dispatch:
inputs:
SOURCE_REGION:
type: choice
default: [ SOME FALLBACK INPUT ]
required: true
options:
- {{ API_RESPONSE[0] }}
- {{ API_RESPONSE[1] }}
- {{ API_RESPONSE[2] }}
- {{ API_RESPONSE[3] }}
Beta Was this translation helpful? Give feedback.
All reactions