none-shall-pass workflow (thevickypedia/Jarvis)

The none-shall-pass workflow from thevickypedia/Jarvis, explained and optimized by Latchkey.

What it does

This is the none-shall-pass workflow from the thevickypedia/Jarvis 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: none-shall-pass

permissions:
  contents: read

on:
  workflow_dispatch:
  push:
    branches:
      - master
    paths:
      - '**/*.md'

jobs:
  none-shall-pass:
    runs-on: thevickypedia-default
    steps:
      - uses: actions/checkout@v4
      - uses: thevickypedia/none-shall-pass@v5

The same workflow, on Latchkey

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

name: none-shall-pass
 
permissions:
  contents: read
 
on:
  workflow_dispatch:
  push:
    branches:
      - master
    paths:
      - '**/*.md'
 
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true
 
jobs:
  none-shall-pass:
    timeout-minutes: 30
    runs-on: thevickypedia-default
    steps:
      - uses: actions/checkout@v4
      - uses: thevickypedia/none-shall-pass@v5
 

What changed

• Cancel superseded runs when a branch or PR gets a newer push.
• 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