Feature Request: GitHub Actions Manual Trigger / Approvals
As far as I can tell, there is no way to manually trigger a workflow execution. If there is, how is it done?
If not, I would like to request an additional event trigger called "manual" that would allow one to arbitrarily trigger an exeuction from the Actions UI within GitHub. My use case is to use Actions as a deployment tool and have the ability to run workflows on older commits (rollbacks) or have production deployment workflows be manually triggered.
In addition to that, the ability to have manual approvals as part of job steps in a workflow would be nice. Similar to the above use case, this would be to have build/tests and development deployments happen automatically, but production deployment steps could be dependent on a manual approval to continue workflow execution.
Solved! Solved! Go to Solution.
Thanks for this feedback! We're always working to improve GitHub and the GitHub Community Forum, and we consider every suggestion we receive. I've logged your feature request in our internal feature request list. Though I can't guarantee anything or share a timeline for this, I can tell you that it's been shared with the appropriate teams for consideration.
Any news regarding this matter?
The manual approval/trigger functionality would be greatly appreciated, and we are sorry that this is lacking from your otherwise great product :) Otherwise we would have started moving other build and deploy-pipelines to Github Actions right away!
Any news about this very important future?
The ability to rollback to a given tag or commit is a critical feature for any enterprise product IMHO.
Y'all; it's a little disingenuous to purport that this is "solved" when it's just a link to another conversation from a product manager confirming that GitHub is considering it.
I'm just saying.
might be possible with the API as per https://help.github.com/en/articles/events-that-trigger-workflows#external-events?
It's very limited right now. It's impossible to pass any custom parameters, and the workflow YAML file must sit on master.