Github Action, Gated release?


Is there a way to have a gate release process in the pipeline?

for example, In terraforms repo, On the master branch, we apply the terraform code on the development environments, but for production, we like to look at the terraform plan to then be able to approve or cancel the run?

In another type of repos, the same scenario still exists, we want to deploy into pre-live environments and then be able to promote a version into production. is there a way to have gated release? 


Have you considered triggering a workflow via GitHub API with repository_dispatch?

You could also trigger a workflow when a release is created (edited, deleted, …)

More information can be found here in the forum, for instance: