Issue Assigner workflow (pytorch/TensorRT)

The Issue Assigner workflow from pytorch/TensorRT, explained and optimized by Latchkey.

What it does

This is the Issue Assigner workflow from the pytorch/TensorRT 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

# This workflow will triage pull requests and apply a label based on the
# paths that are modified in the pull request.
#
# To use this workflow, you will need to set up a .github/labeler.yml
# file with configuration.  For more information, see:
# https://github.com/actions/labeler/blob/master/README.md

name: Issue Assigner
on:
  issues:
    types:
      - labeled
  pull_request_target:
    types:
      - labeled

jobs:
  assign:
    permissions:
      contents: read
      pull-requests: write
    runs-on: ubuntu-latest
    steps:
    - name: Checkout
      uses: actions/checkout@v6

    - name: Assign
      uses: ./.github/actions/assigner
      with:
        repo-token: "${{ secrets.GITHUB_TOKEN }}"
        config-path: .github/code-owners.yml

The same workflow, on Latchkey

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

# This workflow will triage pull requests and apply a label based on the
# paths that are modified in the pull request.
#
# To use this workflow, you will need to set up a .github/labeler.yml
# file with configuration.  For more information, see:
# https://github.com/actions/labeler/blob/master/README.md
 
name: Issue Assigner
on:
  issues:
    types:
      - labeled
  pull_request_target:
    types:
      - labeled
 
jobs:
  assign:
    timeout-minutes: 30
    permissions:
      contents: read
      pull-requests: write
    runs-on: latchkey-small
    steps:
    - name: Checkout
      uses: actions/checkout@v6
 
    - name: Assign
      uses: ./.github/actions/assigner
      with:
        repo-token: "${{ secrets.GITHUB_TOKEN }}"
        config-path: .github/code-owners.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