Trigger Website Update workflow (electerm/electerm)
The Trigger Website Update workflow from electerm/electerm, explained and optimized by Latchkey.
CI health: B - good
Point runs-on at Latchkey and get job timeouts, SHA-pinned actions, self-healing for flaky steps, and up to 58% lower cost, applied automatically.
What it does
This is the Trigger Website Update workflow from the electerm/electerm 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 Website Update
on:
release:
types: [published]
workflow_dispatch:
jobs:
trigger-website-update:
runs-on: ubuntu-latest
environment: build
strategy:
matrix:
repository:
- electerm/electerm.org
- electerm/repos
- electerm/electerm-data-tool
steps:
- name: Trigger ${{ matrix.repository }} repository workflow
uses: peter-evans/repository-dispatch@v2
with:
token: ${{ secrets.PAT_REPO_TOKEN }}
repository: ${{ matrix.repository }}
event-type: electerm-releaseThe same workflow, on Latchkey
Removes redundant runs and caps runaway jobs. Added and changed lines are highlighted.
name: Trigger Website Update on: release: types: [published] workflow_dispatch: jobs: trigger-website-update: timeout-minutes: 30 runs-on: latchkey-small environment: build strategy: matrix: repository: - electerm/electerm.org - electerm/repos - electerm/electerm-data-tool steps: - name: Trigger ${{ matrix.repository }} repository workflow uses: peter-evans/repository-dispatch@v2 with: token: ${{ secrets.PAT_REPO_TOKEN }} repository: ${{ matrix.repository }} event-type: electerm-release
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 useslatchkey-small; pick the runner size that fits the job. - 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 (3 with the matrix expanded) per trigger. On Latchkey the same minutes cost up to 58% less than GitHub-hosted, with zero queue time.