CI workflow (alicebob/miniredis)

The CI workflow from alicebob/miniredis, explained and optimized by Latchkey.

CI health: C - fair

Point runs-on at Latchkey and get run de-duplication, job timeouts, self-healing for flaky steps, and up to 58% lower cost, applied automatically.

Grade your own workflow free or run it on Latchkey →

Source: alicebob/miniredis.github/workflows/ci.yamlLicense MITView source

What it does

This is the CI workflow from the alicebob/miniredis 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

workflow (.yml)

name: CI
on:
  push:
    branches: [ master ]
  pull_request:
    branches: [ master ]
jobs:
  build:
    runs-on: ubuntu-latest
    strategy:
      matrix:
        go: [ '1.17', '1.23', '1.24', '1.25' ]
    name: Go ${{ matrix.go }}
    steps:
    - uses: actions/checkout@v4
    - uses: actions/setup-go@v5
      with:
        go-version: ${{ matrix.go }}

    - name: Cache redis server binary restore
      id: cache-redis-server-binary-restore
      uses: actions/cache/restore@v4
      with:
        path: integration/redis_src/redis-server
        key: "redis-server-binary-${{ hashFiles('integration/get_redis.sh') }}"

    - name: Prevent redis binary rebuild
      if: steps.cache-redis-server-binary-restore.outputs.cache-hit
      run: "touch -m integration/redis_src/redis-server"
      # Make uses modification timestamp to decide if redis-server needs to be rebuilt.
      # In github actions get_redis.sh has modification time set when cloned but redis-server binary has modification
      # time when it was cached (always older than clone). By updating timestamp we avoid unnecessary build.
      # Cache key includes get_redis.sh file hash so there is no risk of using stale binary.

    - name: Test
      run: make ci

    - name: Cache redis server binary save
      if: steps.cache-redis-server-binary-restore.outputs.cache-hit != 'true'
      uses: actions/cache/save@v4
      with:
        path: integration/redis_src/redis-server
        key: ${{ steps.cache-redis-server-binary-restore.outputs.cache-primary-key }}

The same workflow, on Latchkey

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

name: CI
on:
  push:
    branches: [ master ]
  pull_request:
    branches: [ master ]
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true
 
jobs:
  build:
    timeout-minutes: 30
    runs-on: latchkey-small
    strategy:
      matrix:
        go: [ '1.17', '1.23', '1.24', '1.25' ]
    name: Go ${{ matrix.go }}
    steps:
    - uses: actions/checkout@v4
    - uses: actions/setup-go@v5
      with:
        go-version: ${{ matrix.go }}
 
    - name: Cache redis server binary restore
      id: cache-redis-server-binary-restore
      uses: actions/cache/restore@v4
      with:
        path: integration/redis_src/redis-server
        key: "redis-server-binary-${{ hashFiles('integration/get_redis.sh') }}"
 
    - name: Prevent redis binary rebuild
      if: steps.cache-redis-server-binary-restore.outputs.cache-hit
      run: "touch -m integration/redis_src/redis-server"
      # Make uses modification timestamp to decide if redis-server needs to be rebuilt.
      # In github actions get_redis.sh has modification time set when cloned but redis-server binary has modification
      # time when it was cached (always older than clone). By updating timestamp we avoid unnecessary build.
      # Cache key includes get_redis.sh file hash so there is no risk of using stale binary.
 
    - name: Test
      run: make ci
 
    - name: Cache redis server binary save
      if: steps.cache-redis-server-binary-restore.outputs.cache-hit != 'true'
      uses: actions/cache/save@v4
      with:
        path: integration/redis_src/redis-server
        key: ${{ steps.cache-redis-server-binary-restore.outputs.cache-primary-key }}

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.
Cancel superseded runs when a branch or PR gets a newer push.
Add a job timeout so a hung step cannot burn hours of runner time.

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

Actions used in this workflow

actions/checkout actions/setup-go actions/cache