Octoslash workflow (spf13/viper)

The Octoslash workflow from spf13/viper, explained and optimized by Latchkey.

What it does

This is the Octoslash workflow from the spf13/viper 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

name: Octoslash

on: issue_comment

permissions:
  issues: write
  pull-requests: write

jobs:
  run:
    name: Run
    runs-on: ubuntu-latest
    steps:
      - name: Checkout repository
        uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2

      - name: Octoslash
        uses: sagikazarmark/octoslash-action@v0

The same workflow, on Latchkey

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

name: Octoslash
 
on: issue_comment
 
permissions:
  issues: write
  pull-requests: write
 
jobs:
  run:
    timeout-minutes: 30
    name: Run
    runs-on: latchkey-small
    steps:
      - name: Checkout repository
        uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
 
      - name: Octoslash
        uses: sagikazarmark/octoslash-action@v0
 

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.

Actions used in this workflow