Trigger site deploy workflow (aframevr/aframe)

The Trigger site deploy workflow from aframevr/aframe, explained and optimized by Latchkey.

What it does

This is the Trigger site deploy workflow from the aframevr/aframe 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: Trigger site deploy

on:
  push:
    branches:
      - master
      - 'docs-v*'
    paths:
      - 'docs/**'

permissions: {}

jobs:
  trigger:
    runs-on: ubuntu-latest
    steps:
      - name: Trigger aframevr.github.io deploy
        run: |
          gh api repos/aframevr/aframevr.github.io/dispatches \
            -f event_type=deploy
        env:
          GH_TOKEN: ${{ secrets.DEPLOY_PAT }}

The same workflow, on Latchkey

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

name: Trigger site deploy
 
on:
  push:
    branches:
      - master
      - 'docs-v*'
    paths:
      - 'docs/**'
 
permissions: {}
 
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true
 
jobs:
  trigger:
    timeout-minutes: 30
    runs-on: latchkey-small
    steps:
      - name: Trigger aframevr.github.io deploy
        run: |
          gh api repos/aframevr/aframevr.github.io/dispatches \
            -f event_type=deploy
        env:
          GH_TOKEN: ${{ secrets.DEPLOY_PAT }}
 

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.
• 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.

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