Docs Notify workflow (yuzutech/kroki)
The Docs Notify workflow from yuzutech/kroki, 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 Docs Notify workflow from the yuzutech/kroki 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: Docs Notify
on:
push:
paths:
- 'docs/**'
branches:
- main
jobs:
trigger_publish:
runs-on: ubuntu-latest
steps:
- name: Notify docs.kroki.io
uses: peter-evans/repository-dispatch@v4.0.1
with:
token: ${{ secrets.REPO_ACCESS_TOKEN }}
repository: yuzutech/docs.kroki.io
event-type: kroki
The same workflow, on Latchkey
Removes redundant runs and caps runaway jobs. Added and changed lines are highlighted.
name: Docs Notify on: push: paths: - 'docs/**' branches: - main concurrency: group: ${{ github.workflow }}-${{ github.ref }} cancel-in-progress: true jobs: trigger_publish: timeout-minutes: 30 runs-on: latchkey-small steps: - name: Notify docs.kroki.io uses: peter-evans/repository-dispatch@v4.0.1 with: token: ${{ secrets.REPO_ACCESS_TOKEN }} repository: yuzutech/docs.kroki.io event-type: kroki
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.