GitHub Actions Workflows - deployment approval timeouts

[larryclaman]

When using GitHub Actions Workflows with deployment approvals, I'm looking for the ability to time-out a workflow if no one approves it within a specified period of time.

As a comparison, when I've used Azure DevOps Pipelines, I can add a manual approval to a pipeline, and set that approval to time out after X minutes. Eg if no one approves it after X minutes, the pipeline is canceled (as if someone clicked 'not approved')

However, when using GitHub Actions Workflows with environment approvals, the documentation says "If a job is not approved within 30 days, the workflow run will be automatically canceled". But it doesn't appear that you can customize the 30 day timeout to something more useful; eg, hours or minutes. So unless you manually clean it up, you can end up with a lot of workflows "stuck" in the waiting-for-approval state.

Please add the capability to customize the 30 day timeout to something user specified.

[HariSekhon]

This is especially important because unapproved deployments can backlog and prevent new ones from being able to run

[Orrimp]

With a self-hosted runner 10 PRs per Week, 30 Days is a bit excessive :D
For us one week waiting would be enough. Therefore please make it configurarble

[apoclyps]

The ability to configure a timeout for deployments awaiting approval would be hugely beneficial. I work on a team that typically deploys in the range of 10-20 a day from Monday to Friday across a range of services and the number of Github Action Workflows awaiting approval can be significant.

A configurable timeout would be ideal for the required approval steps to avoid waiting 30 days for a cleanup operation to happen

[nemmeviu]

+1

[melendezd]

Being able to customize the timeout for deployment approvals would be very useful. We are trying to migrate our deployments to GitHub Actions and not having this feature complicates things.

[AFMiziara]

+1

[micd]

+1

[tfglasswing]

+2

[nnamacha]

+1