delete-builds workflow (arabcoders/ytptube)

The delete-builds workflow from arabcoders/ytptube, explained and optimized by Latchkey.

What it does

This is the delete-builds workflow from the arabcoders/ytptube repository, a real project running GitHub Actions. It is shown here with attribution under its MIT license.

Below, Latchkey shows a faster, safer version produced by its optimization engine.

The workflow

name: delete-builds

on:
  workflow_dispatch:
    inputs:
      logLevel:
        description: "Log level"
        required: true
        default: "warning"
        type: choice
        options:
          - info
          - warning
          - debug

jobs:
  delete-builds:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/delete-package-versions@v4
        with:
          package-name: "ytptube"
          package-type: "container"
          min-versions-to-keep: 20

The same workflow, on Latchkey

Removes redundant runs and caps runaway jobs. Added and changed lines are highlighted.

name: delete-builds
 
on:
  workflow_dispatch:
    inputs:
      logLevel:
        description: "Log level"
        required: true
        default: "warning"
        type: choice
        options:
          - info
          - warning
          - debug
 
jobs:
  delete-builds:
    timeout-minutes: 30
    runs-on: latchkey-small
    steps:
      - uses: actions/delete-package-versions@v4
        with:
          package-name: "ytptube"
          package-type: "container"
          min-versions-to-keep: 20
 

What changed

• Run on Latchkey managed runners with one line (runs-on), which apply the fixes below automatically and self-heal transient failures. This example uses latchkey-small; pick the runner size that fits the job.
• Add a job timeout so a hung step cannot burn hours of runner time.

This workflow runs 1 job per trigger. On Latchkey the same minutes cost up to 58% less than GitHub-hosted, with zero queue time.