Add issue or pull request to Project workflow (gorilla/mux)

The Add issue or pull request to Project workflow from gorilla/mux, explained and optimized by Latchkey.

What it does

This is the Add issue or pull request to Project workflow from the gorilla/mux 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

# Add all the issues created to the project.
name: Add issue or pull request to Project

on:
  issues:
    types:
      - opened
  pull_request_target:
    types:
      - opened
      - reopened

jobs:
  add-to-project:
    runs-on: ubuntu-latest
    steps:
      - name: Add issue to project
        uses: actions/add-to-project@v0.5.0
        with:
          project-url: https://github.com/orgs/gorilla/projects/4
          github-token: ${{ secrets.ADD_TO_PROJECT_TOKEN }}

The same workflow, on Latchkey

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

# Add all the issues created to the project.
name: Add issue or pull request to Project
 
on:
  issues:
    types:
      - opened
  pull_request_target:
    types:
      - opened
      - reopened
 
jobs:
  add-to-project:
    timeout-minutes: 30
    runs-on: latchkey-small
    steps:
      - name: Add issue to project
        uses: actions/add-to-project@v0.5.0
        with:
          project-url: https://github.com/orgs/gorilla/projects/4
          github-token: ${{ secrets.ADD_TO_PROJECT_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.