Auto Label Issue workflow (appwrite/appwrite)

The Auto Label Issue workflow from appwrite/appwrite, explained and optimized by Latchkey.

What it does

This is the Auto Label Issue workflow from the appwrite/appwrite repository, a real project running GitHub Actions. It is shown here with attribution under its BSD-3-Clause license.

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

The workflow

name: Auto Label Issue

on:
  issues:
    types: [opened]

permissions:
  issues: write
  contents: read

jobs:
  labeler:
    runs-on: ubuntu-latest
    steps:
      - name: Issue Labeler
        uses: github/issue-labeler@c1b0f9f52a63158c4adc09425e858e87b32e9685 # v3.4
        with:
          configuration-path: .github/labeler.yml
          enable-versioned-regex: false
          include-title: 1
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

The same workflow, on Latchkey

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

name: Auto Label Issue
 
on:
  issues:
    types: [opened]
 
permissions:
  issues: write
  contents: read
 
jobs:
  labeler:
    timeout-minutes: 30
    runs-on: latchkey-small
    steps:
      - name: Issue Labeler
        uses: github/issue-labeler@c1b0f9f52a63158c4adc09425e858e87b32e9685 # v3.4
        with:
          configuration-path: .github/labeler.yml
          enable-versioned-regex: false
          include-title: 1
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_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.

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