auto-assignment workflow (keras-team/keras-hub)

The auto-assignment workflow from keras-team/keras-hub, explained and optimized by Latchkey.

What it does

This is the auto-assignment workflow from the keras-team/keras-hub 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: auto-assignment
on:
  issues:
    types:
      - opened
  pull_request_target:
    types:
      - opened

permissions:
  contents: read
  issues: write
  pull-requests: write

jobs:
  welcome:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v7
      - uses: actions/github-script@v9
        with:
          script: |
            const script = require('./\.github/workflows/scripts/auto-assignment.js')
            script({github, context})

The same workflow, on Latchkey

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

name: auto-assignment
on:
  issues:
    types:
      - opened
  pull_request_target:
    types:
      - opened
 
permissions:
  contents: read
  issues: write
  pull-requests: write
 
jobs:
  welcome:
    timeout-minutes: 30
    runs-on: latchkey-small
    steps:
      - uses: actions/checkout@v7
      - uses: actions/github-script@v9
        with:
          script: |
            const script = require('./\.github/workflows/scripts/auto-assignment.js')
            script({github, context})
 

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.

Actions used in this workflow