Publish Wiki workflow (MahjongRepository/mahjong)

The Publish Wiki workflow from MahjongRepository/mahjong, explained and optimized by Latchkey.

What it does

This is the Publish Wiki workflow from the MahjongRepository/mahjong 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: Publish Wiki

on:
  push:
    branches: [master]
    paths:
      - .github/wiki/**

permissions:
  contents: write

jobs:
  publish:
    name: Publish Wiki
    runs-on: ubuntu-latest
    timeout-minutes: 5

    steps:
      - uses: actions/checkout@v6
      - uses: Andrew-Chen-Wang/github-wiki-action@v5
        with:
          path: .github/wiki/

The same workflow, on Latchkey

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

name: Publish Wiki
 
on:
  push:
    branches: [master]
    paths:
      - .github/wiki/**
 
permissions:
  contents: write
 
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true
 
jobs:
  publish:
    name: Publish Wiki
    runs-on: latchkey-small
    timeout-minutes: 5
 
    steps:
      - uses: actions/checkout@v6
      - uses: Andrew-Chen-Wang/github-wiki-action@v5
        with:
          path: .github/wiki/
 

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

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