Skip to content
Latchkey

Pull Request Labels workflow (okteto/okteto)

The Pull Request Labels workflow from okteto/okteto, explained and optimized by Latchkey.

C

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.

Grade your own workflow free or run it on Latchkey →
Source: okteto/okteto.github/workflows/required-labels.ymlLicense Apache-2.0View source

What it does

This is the Pull Request Labels workflow from the okteto/okteto repository, a real project running GitHub Actions. It is shown here with attribution under its Apache-2.0 license.

Below, Latchkey shows a faster, safer version produced by its optimization engine.

The workflow

workflow (.yml)
name: "Pull Request Labels"
on:
  pull_request:
    types:
      - opened
      - labeled
      - unlabeled
      - synchronize
jobs:
  label:
    runs-on: ubuntu-latest
    steps:
      - uses: mheap/github-action-required-labels@v5
        with:
          mode: exactly
          count: 1
          # yamllint disable-line rule:line-length
          labels: "release/internal, release/bug-fix, release/new-feature, release/breaking-change"

The same workflow, on Latchkey

Removes redundant runs and caps runaway jobs. Added and changed lines are highlighted.

name: "Pull Request Labels"
on:
  pull_request:
    types:
      - opened
      - labeled
      - unlabeled
      - synchronize
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true
 
jobs:
  label:
    timeout-minutes: 30
    runs-on: latchkey-small
    steps:
      - uses: mheap/github-action-required-labels@v5
        with:
          mode: exactly
          count: 1
          # yamllint disable-line rule:line-length
          labels: "release/internal, release/bug-fix, release/new-feature, release/breaking-change"
 

What changed

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.