add-to-project workflow (standard/standard)

The add-to-project workflow from standard/standard, explained and optimized by Latchkey.

What it does

This is the add-to-project workflow from the standard/standard 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

on:
  pull_request:
    types: [opened]
  issues:
    types: [opened]

jobs:
  add-to-project:
    uses: standard/.github/.github/workflows/add-to-project.yaml@master
    secrets: inherit

The same workflow, on Latchkey

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

on:
  pull_request:
    types: [opened]
  issues:
    types: [opened]
 
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true
 
jobs:
  add-to-project:
    timeout-minutes: 30
    uses: standard/.github/.github/workflows/add-to-project.yaml@master
    secrets: inherit
 

What changed

• Cancel superseded runs when a branch or PR gets a newer push.
• Add a job timeout so a hung step cannot burn hours of runner time.

1 third-party action is referenced by a movable tag. Pin it to the commit SHA (Latchkey resolves and applies this automatically) so a repointed tag cannot change what runs.

This workflow runs 1 job per trigger. On Latchkey the same minutes cost up to 58% less than GitHub-hosted, with zero queue time.