Label PRs from globs workflow (jaredpalmer/razzle)
The Label PRs from globs workflow from jaredpalmer/razzle, 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 Label PRs from globs workflow from the jaredpalmer/razzle 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
# Automatically label PRs every hour based on your .github/labels.yaml:
#
# This workflow will triage pull requests and apply a label based on the
# paths that are modified in the pull request.
#
# To use this workflow, you will need to set up a .github/labeler.yml
# file with configuration. For more information, see:
# https://github.com/actions/labeler/blob/master/README.md
name: "Label PRs from globs"
on:
schedule:
- cron: "0 1 * * *"
jobs:
execute:
runs-on: ubuntu-latest
steps:
- name: Label PRs
uses: jpmcb/prow-github-actions@v1.0.0
with:
jobs: 'pr-labeler'
github-token: "${{ secrets.GITHUB_TOKEN }}"
The same workflow, on Latchkey
Removes redundant runs and caps runaway jobs. Added and changed lines are highlighted.
# Automatically label PRs every hour based on your .github/labels.yaml: # # This workflow will triage pull requests and apply a label based on the # paths that are modified in the pull request. # # To use this workflow, you will need to set up a .github/labeler.yml # file with configuration. For more information, see: # https://github.com/actions/labeler/blob/master/README.md name: "Label PRs from globs" on: schedule: - cron: "0 1 * * *" jobs: execute: timeout-minutes: 30 runs-on: latchkey-small steps: - name: Label PRs uses: jpmcb/prow-github-actions@v1.0.0 with: jobs: 'pr-labeler' github-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.
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.