Cleanup Review Apps workflow (badges/shields)

The Cleanup Review Apps workflow from badges/shields, explained and optimized by Latchkey.

What it does

This is the Cleanup Review Apps workflow from the badges/shields repository, a real project running GitHub Actions. It is shown here with attribution under its Apache-2.0 license.

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

The workflow

name: Cleanup Review Apps
on:
  schedule:
    - cron: '0 7 * * *'
    # At 07:00, daily
  workflow_dispatch:

jobs:
  cleanup-review-apps:
    runs-on: ubuntu-latest
    environment: 'Review Apps'
    steps:
      - uses: actions/checkout@v7
      - uses: superfly/flyctl-actions/setup-flyctl@master

      - name: install jq
        run: |
          sudo apt-get -qq update
          sudo apt-get install -y jq

      - run: .github/scripts/cleanup-review-apps.sh
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
          FLY_API_TOKEN: ${{ secrets.FLY_API_TOKEN }}

The same workflow, on Latchkey

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

name: Cleanup Review Apps
on:
  schedule:
    - cron: '0 7 * * *'
    # At 07:00, daily
  workflow_dispatch:
 
jobs:
  cleanup-review-apps:
    timeout-minutes: 30
    runs-on: latchkey-small
    environment: 'Review Apps'
    steps:
      - uses: actions/checkout@v7
      - uses: superfly/flyctl-actions/setup-flyctl@master
 
      - name: install jq
        run: |
          sudo apt-get -qq update
          sudo apt-get install -y jq
 
      - run: .github/scripts/cleanup-review-apps.sh
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
          FLY_API_TOKEN: ${{ secrets.FLY_API_TOKEN }}
 

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.

1 third-party action is referenced by a movable tag. Pin it to the commit SHA (Latchkey resolves and applies this automatically) so a repointed tag cannot change what runs.

What Latchkey heals here

This workflow has steps that commonly fail on transient issues (network, registries, flaky browsers). On Latchkey managed runners they are detected, retried, and self-healed instead of failing your build:

• Dependency installs

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

Actions used in this workflow