Labeler workflow (KapJI/capital-gains-calculator)
The Labeler workflow from KapJI/capital-gains-calculator, explained and optimized by Latchkey.
A
CI health: A - excellent
Point runs-on at Latchkey and get job timeouts, self-healing for flaky steps, and up to 58% lower cost, applied automatically.
What it does
This is the Labeler workflow from the KapJI/capital-gains-calculator 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
workflow (.yml)
name: Labeler
on:
pull_request_target:
branches:
- main
jobs:
triage:
name: Triage
runs-on: ubuntu-latest
steps:
- name: Run Pull Request Labeler
uses: actions/labeler@main
with:
repo-token: "${{ secrets.GITHUB_TOKEN }}"
The same workflow, on Latchkey
Removes redundant runs and caps runaway jobs. Added and changed lines are highlighted.
name: Labeler on: pull_request_target: branches: - main jobs: triage: timeout-minutes: 30 name: Triage runs-on: latchkey-small steps: - name: Run Pull Request Labeler uses: actions/labeler@main with: repo-token: "${{ secrets.GITHUB_TOKEN }}"
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.
This workflow runs 1 job per trigger. On Latchkey the same minutes cost up to 58% less than GitHub-hosted, with zero queue time.