Verify template changes are committed workflow (Shpota/goxygen)

The Verify template changes are committed workflow from Shpota/goxygen, explained and optimized by Latchkey.

What it does

This is the Verify template changes are committed workflow from the Shpota/goxygen 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: Verify template changes are committed
on: [push]
jobs:
  verify:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-go@v5
        with:
          go-version: '1.23'
      - name: Generate and format code
        run: |
          go generate ./...
          go fmt ./...
      - name: Check for changes
        run: |
          if [ -n "$(git status --porcelain)" ]; then
            echo "Generated files are not up to date!"
            git status
            exit 1
          fi

The same workflow, on Latchkey

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

name: Verify template changes are committed
on: [push]
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true
 
jobs:
  verify:
    timeout-minutes: 30
    runs-on: latchkey-small
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-go@v5
        with:
          go-version: '1.23'
      - name: Generate and format code
        run: |
          go generate ./...
          go fmt ./...
      - name: Check for changes
        run: |
          if [ -n "$(git status --porcelain)" ]; then
            echo "Generated files are not up to date!"
            git status
            exit 1
          fi

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 per trigger. On Latchkey the same minutes cost up to 58% less than GitHub-hosted, with zero queue time.

Actions used in this workflow