Closed micheal-hill-sportsbet closed 1 month ago
Hi,
Thanks for submitting this request.
For adding WAITING to the status filter - Done, should be released soon.
Regarding reviewing deployments. I haven't used deployments on GitHub actions myself, I would need to set up a repository that uses them, and then I can develop it. It would take a bit longer.
Reviewing deployments implemented in v2024.2.9.
Is your feature request related to a problem? Please describe. I guess there are two pain points that I'd like to solve here.
Status
dropdown is missing aWaiting
option. Workflows in this state do appear in the list of workflow runs when there is no filterSee below for some fragments (some parts redacted) of API responses for a run in 'waiting' state.
`GET /repos///actions/runs/10551800200`
This one is pretty big, and probably most of the response isn't so useful, so I've removed a bunch of fields that are probably irrelevant. ```json { "id": 10551800200, "name": "`GET /repos///actions/runs/10551800200/pending_deployments`
```json [ { "environment": { "id": 2216775239, "node_id": "EN_kwDOJeopkM6EIU5H", "name": "branch_cleanup", "url": "https://api.github.com/repos/In addition, I can currently review the deployment via CLI using the deployment review API
Describe the solution you'd like I'd like:
status == 'waiting'
so that I can easily see which workflows are currently pending deployment approval.Describe alternatives you've considered Currently I use a combination of GH web UI for these tasks and CLI. This works, but is a bit annoying - especially for trivial deployments.
Adding this functionality probably won't completely remove my need to access the web UI (some deployment approvals are not so simple to review in IntelliJ), but it would probably eliminate my use of CLI for these deployment steps.
Additional context My organisation uses deployment approval steps extensively, both for branch cleanup (as in the example above) jobs and along the path to production. Unfortunately this pattern is not one that I can easily change (a combination of regulation and org policy), but it would be great if I could avoid switching apps a bit more to deal with this pattern.
Upvote & Fund