Pull Request Labeler workflow (kr8s-org/kr8s)
The Pull Request Labeler workflow from kr8s-org/kr8s, 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 Pull Request Labeler workflow from the kr8s-org/kr8s 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
name: "Pull Request Labeler"
on:
- pull_request_target
jobs:
triage:
permissions:
contents: read
pull-requests: write
runs-on: ubuntu-latest
steps:
- uses: actions/labeler@v4
name: File Path Labeler
- uses: TimonVS/pr-labeler-action@v5
name: Conventional Commits Labeler
with:
repo-token: ${{ secrets.GITHUB_TOKEN }}
configuration-path: .github/conventional-commits-labeler.yml
The same workflow, on Latchkey
Removes redundant runs and caps runaway jobs. Added and changed lines are highlighted.
name: "Pull Request Labeler" on: - pull_request_target jobs: triage: timeout-minutes: 30 permissions: contents: read pull-requests: write runs-on: latchkey-small steps: - uses: actions/labeler@v4 name: File Path Labeler - uses: TimonVS/pr-labeler-action@v5 name: Conventional Commits Labeler with: repo-token: ${{ secrets.GITHUB_TOKEN }} configuration-path: .github/conventional-commits-labeler.yml
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 per trigger. On Latchkey the same minutes cost up to 58% less than GitHub-hosted, with zero queue time.