Auto Assign workflow (dragonflyoss/dragonfly)

The Auto Assign workflow from dragonflyoss/dragonfly, explained and optimized by Latchkey.

What it does

This is the Auto Assign workflow from the dragonflyoss/dragonfly 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 Assign'

on:
  pull_request_target:
    types: [opened, reopened, ready_for_review]

permissions:
  pull-requests: write

jobs:
  add-assignee:
    runs-on: ubuntu-latest
    steps:
      - uses: kentaro-m/auto-assign-action@e4bac10e264c621dbfddcba9b25d1f9d79c3117a

The same workflow, on Latchkey

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

name: 'Auto Assign'
 
on:
  pull_request_target:
    types: [opened, reopened, ready_for_review]
 
permissions:
  pull-requests: write
 
jobs:
  add-assignee:
    timeout-minutes: 30
    runs-on: latchkey-small
    steps:
      - uses: kentaro-m/auto-assign-action@e4bac10e264c621dbfddcba9b25d1f9d79c3117a
 

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.