workflow_dispach to have dynamic inputs parameters #11795
Replies: 130 comments 42 replies
-
Yes, GitHub action inputs really need this! Almost crucial for any CICD platform to avoid errors from operators who perform manual jobs on a frequent basis. Please get this feature in ASAP! |
Beta Was this translation helpful? Give feedback.
-
This is a neat idea. Thanks for the feedback! We'll put this on the backlog. |
Beta Was this translation helpful? Give feedback.
-
+1 on this. Will add huge benefits |
Beta Was this translation helpful? Give feedback.
-
How's that
m.blanco
…On Wed, Apr 13, 2022, 12:38 AM marvader ***@***.***> wrote:
+1 on this. Will add huge benefits
—
Reply to this email directly, view it on GitHub
<#11795 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AYPOVFDUEZBBKT6F4IZSSGLVEZ2Y3ANCNFSM5O4B2U5Q>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
I'd love a dynamic input, let me run some scripts to build a list. |
Beta Was this translation helpful? Give feedback.
-
Hi, is there any update on this because I need to implement it now in my current requirement or any workarounds for how to pass a variable as inputs would be very helpful. |
Beta Was this translation helpful? Give feedback.
-
Plus One for this. In my companies work we add deployment environments and want to be able to allow the person running the action to select the environment to deploy to. Right now that means modifying every workflow to add the additional environment to the workflow_dispatch inputs. |
Beta Was this translation helpful? Give feedback.
-
Plus one on this. |
Beta Was this translation helpful? Give feedback.
-
This question is discussed from 2022, but there is no progress until now. I would like to share my workaround approach. Since my company's projects are all private repos in the GitHub Enterprise, there are few people who can use GitHub Actions, so I developed a Chrome extension to solve this problem and use the extension's scripts to handle dynamic options. Do not set type: choice inputs in the yaml and the workflow will not check the value of the input. |
Beta Was this translation helpful? Give feedback.
-
Any update on this? I could really use this feature |
Beta Was this translation helpful? Give feedback.
-
Thank you for introducing the workflow_dispatch for manual jobs.
It'd be good to have dynamic input parameters so that with one job.yml, we can present just one form input to the operator.
For example, on select choices <stg, prod>, we can hide/show/change the other options, before the operator clicks the Run Workflow.
Beta Was this translation helpful? Give feedback.
All reactions