Label Pull Requests workflow (nextauthjs/next-auth)

The Label Pull Requests workflow from nextauthjs/next-auth, explained and optimized by Latchkey.

What it does

This is the Label Pull Requests workflow from the nextauthjs/next-auth repository, a real project running GitHub Actions. It is shown here with attribution under its ISC license.

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

The workflow

# https://github.com/actions/labeler#create-workflow

name: Label Pull Requests

on:
  pull_request_target:

jobs:
  prs:
    name: Triage
    runs-on: ubuntu-latest
    steps:
      - uses: actions/labeler@v4
        with:
          repo-token: "${{ secrets.GITHUB_TOKEN }}"
          configuration-path: ".github/pr-labeler.yml"

The same workflow, on Latchkey

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

# https://github.com/actions/labeler#create-workflow
 
name: Label Pull Requests
 
on:
  pull_request_target:
 
jobs:
  prs:
    timeout-minutes: 30
    name: Triage
    runs-on: latchkey-small
    steps:
      - uses: actions/labeler@v4
        with:
          repo-token: "${{ secrets.GITHUB_TOKEN }}"
          configuration-path: ".github/pr-labeler.yml"
 

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