Conventional Commit Labels workflow (kagent-dev/kagent)

The Conventional Commit Labels workflow from kagent-dev/kagent, explained and optimized by Latchkey.

What it does

This is the Conventional Commit Labels workflow from the kagent-dev/kagent 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

name: Conventional Commit Labels

on:
  pull_request_target:
    types: [opened, edited]

jobs:
  label-by-title:
    runs-on: ubuntu-latest
    permissions:
      contents: read
      pull-requests: write
    steps:
      - uses: bcoe/conventional-release-labels@v1
        with:
          type_labels: |
            {
              "feat": "enhancement",
              "fix": "bug",
              "docs": "documentation",
              "test": "testing"
            }

The same workflow, on Latchkey

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

name: Conventional Commit Labels
 
on:
  pull_request_target:
    types: [opened, edited]
 
jobs:
  label-by-title:
    timeout-minutes: 30
    runs-on: latchkey-small
    permissions:
      contents: read
      pull-requests: write
    steps:
      - uses: bcoe/conventional-release-labels@v1
        with:
          type_labels: |
            {
              "feat": "enhancement",
              "fix": "bug",
              "docs": "documentation",
              "test": "testing"
            }
 

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 uses latchkey-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.