Add to Project workflow (fastapi/asyncer)

The Add to Project workflow from fastapi/asyncer, explained and optimized by Latchkey.

What it does

This is the Add to Project workflow from the fastapi/asyncer 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: Add to Project

on:
  pull_request_target: # zizmor: ignore[dangerous-triggers]
  issues:
    types:
      - opened
      - reopened

permissions: {}

jobs:
  add-to-project:
    name: Add to project
    runs-on: ubuntu-latest
    steps:
      - uses: actions/add-to-project@5afcf98fcd03f1c2f92c3c83f58ae24323cc57fd # v2.0.0
        with:
          project-url: https://github.com/orgs/fastapi/projects/2
          github-token: ${{ secrets.PROJECTS_TOKEN }} # zizmor: ignore[secrets-outside-env]

The same workflow, on Latchkey

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

name: Add to Project
 
on:
  pull_request_target: # zizmor: ignore[dangerous-triggers]
  issues:
    types:
      - opened
      - reopened
 
permissions: {}
 
jobs:
  add-to-project:
    timeout-minutes: 30
    name: Add to project
    runs-on: latchkey-small
    steps:
      - uses: actions/add-to-project@5afcf98fcd03f1c2f92c3c83f58ae24323cc57fd # v2.0.0
        with:
          project-url: https://github.com/orgs/fastapi/projects/2
          github-token: ${{ secrets.PROJECTS_TOKEN }} # zizmor: ignore[secrets-outside-env]
 

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.