PR Labeler workflow (DNSControl/dnscontrol)

The PR Labeler workflow from DNSControl/dnscontrol, explained and optimized by Latchkey.

What it does

This is the PR Labeler workflow from the DNSControl/dnscontrol repository, a real project running GitHub Actions. It is shown here with attribution under its MIT license.

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

The workflow

name: PR Labeler

on:
  pull_request_target:
    types:
      - opened
      - synchronize

jobs:
  label:
    runs-on: ubuntu-latest
    permissions:
      contents: read
      pull-requests: write
    steps:
      - uses: actions/checkout@v7
      - uses: actions/labeler@v6
        with:
          configuration-path: .github/labeler.yml

The same workflow, on Latchkey

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

name: PR Labeler
 
on:
  pull_request_target:
    types:
      - opened
      - synchronize
 
jobs:
  label:
    timeout-minutes: 30
    runs-on: latchkey-small
    permissions:
      contents: read
      pull-requests: write
    steps:
      - uses: actions/checkout@v7
      - uses: actions/labeler@v6
        with:
          configuration-path: .github/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