Auto Assign issue to Project workflow (software-mansion/protostar)

The Auto Assign issue to Project workflow from software-mansion/protostar, explained and optimized by Latchkey.

What it does

This is the Auto Assign issue to Project workflow from the software-mansion/protostar 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: Auto Assign issue to Project

on:
  issues:
    types: [opened]

jobs:
  assign_one_project:
    runs-on: ubuntu-20.04
    name: Assign to Project
    steps:
    - name: Assign new issues to the project board
      uses: actions/add-to-project@v0.1.0
      with:
        project-url: https://github.com/orgs/software-mansion/projects/2
        github-token: ${{ secrets.PROTOSTAR_GITHUB_TOKEN }}

The same workflow, on Latchkey

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

name: Auto Assign issue to Project
 
on:
  issues:
    types: [opened]
 
jobs:
  assign_one_project:
    timeout-minutes: 30
    runs-on: latchkey-small
    name: Assign to Project
    steps:
    - name: Assign new issues to the project board
      uses: actions/add-to-project@v0.1.0
      with:
        project-url: https://github.com/orgs/software-mansion/projects/2
        github-token: ${{ secrets.PROTOSTAR_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.