Pull Request Labeler workflow (nyu-mlab/iot-inspector-client)

The Pull Request Labeler workflow from nyu-mlab/iot-inspector-client, explained and optimized by Latchkey.

What it does

This is the Pull Request Labeler workflow from the nyu-mlab/iot-inspector-client 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: Pull Request Labeler
on:
  - pull_request_target

# Automatically cancel any previous workflow on a new push.
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}-${{ github.event_name }}
  cancel-in-progress: true

jobs:
  triage:
    permissions:
      contents: read
      pull-requests: write
      issues: write
    runs-on: ubuntu-22.04
    steps:
      - uses: actions/labeler@v4
        with:
          repo-token: "${{ secrets.GITHUB_TOKEN }}"

The same workflow, on Latchkey

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

name: Pull Request Labeler
on:
  - pull_request_target
 
# Automatically cancel any previous workflow on a new push.
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}-${{ github.event_name }}
  cancel-in-progress: true
 
jobs:
  triage:
    timeout-minutes: 30
    permissions:
      contents: read
      pull-requests: write
      issues: write
    runs-on: latchkey-small
    steps:
      - uses: actions/labeler@v4
        with:
          repo-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.

Actions used in this workflow