Trigger Website Rebuild (Docs Updated) workflow (jackwener/OpenCLI)
The Trigger Website Rebuild (Docs Updated) workflow from jackwener/OpenCLI, explained and optimized by Latchkey.
CI health: C - fair
Point runs-on at Latchkey and get run de-duplication, 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 Rebuild (Docs Updated) workflow from the jackwener/OpenCLI repository, a real project running GitHub Actions. It is shown here with attribution under its Apache-2.0 license.
Below, Latchkey shows a faster, safer version produced by its optimization engine.
The workflow
name: Trigger Website Rebuild (Docs Updated)
on:
push:
branches: [main]
paths: ['docs/**']
jobs:
dispatch:
runs-on: ubuntu-latest
steps:
- name: Trigger opencli-website rebuild
uses: peter-evans/repository-dispatch@v4
with:
token: ${{ secrets.WEBSITE_DEPLOY_TOKEN }}
repository: jackwener/opencli-website
event-type: docs-updated
The same workflow, on Latchkey
Removes redundant runs and caps runaway jobs. Added and changed lines are highlighted.
name: Trigger Website Rebuild (Docs Updated) on: push: branches: [main] paths: ['docs/**'] concurrency: group: ${{ github.workflow }}-${{ github.ref }} cancel-in-progress: true jobs: dispatch: timeout-minutes: 30 runs-on: latchkey-small steps: - name: Trigger opencli-website rebuild uses: peter-evans/repository-dispatch@v4 with: token: ${{ secrets.WEBSITE_DEPLOY_TOKEN }} repository: jackwener/opencli-website event-type: docs-updated
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. - 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.