Benchmark Trigger by Label workflow (napari/napari)
The Benchmark Trigger by Label workflow from napari/napari, explained and optimized by Latchkey.
C
CI health: C - fair
Run this on Latchkey for self-healing, caching, and up to 58% lower cost.
Grade your own workflow free or run it on Latchkey →What it does
This is the Benchmark Trigger by Label workflow from the napari/napari repository, a real project running GitHub Actions. It is shown here with attribution under its BSD-3-Clause license.
Below, Latchkey shows a faster, safer version produced by its optimization engine.
The workflow
workflow (.yml)
name: Benchmark Trigger by Label
on:
pull_request:
types: [labeled]
permissions:
contents: read
issues: write
jobs:
trigger-benchmarks:
if: github.event.label.name == 'run-benchmarks'
uses: ./.github/workflows/benchmarks.yml
secrets: inherit
The same workflow, on Latchkey
Removes redundant runs and caps runaway jobs. Added and changed lines are highlighted.
name: Benchmark Trigger by Label on: pull_request: types: [labeled] permissions: contents: read issues: write concurrency: group: ${{ github.workflow }}-${{ github.ref }} cancel-in-progress: true jobs: trigger-benchmarks: timeout-minutes: 30 if: github.event.label.name == 'run-benchmarks' uses: ./.github/workflows/benchmarks.yml 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.
This workflow runs 1 job per trigger. On Latchkey the same minutes cost up to 58% less than GitHub-hosted, with zero queue time.