Lint sh workflow (databus23/helm-diff)
The Lint sh workflow from databus23/helm-diff, explained and optimized by Latchkey.
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.
What it does
This is the Lint sh workflow from the databus23/helm-diff 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: Lint sh
on:
push:
branches: [master]
paths: ['install-binary.sh']
pull_request:
branches: [master]
paths: ['install-binary.sh']
jobs:
lint-sh:
name: Lint install-binary.sh
runs-on: ubuntu-latest
if: "!contains(github.event.head_commit.message, '[ci skip]')"
continue-on-error: true
steps:
- uses: actions/checkout@v7
- uses: luizm/action-sh-checker@v0.10.0
with:
sh_checker_exclude: 'scripts'
sh_checker_checkbashisms_enable: true
The same workflow, on Latchkey
Removes redundant runs and caps runaway jobs. Added and changed lines are highlighted.
name: Lint sh on: push: branches: [master] paths: ['install-binary.sh'] pull_request: branches: [master] paths: ['install-binary.sh'] concurrency: group: ${{ github.workflow }}-${{ github.ref }} cancel-in-progress: true jobs: lint-sh: timeout-minutes: 30 name: Lint install-binary.sh runs-on: latchkey-small if: "!contains(github.event.head_commit.message, '[ci skip]')" continue-on-error: true steps: - uses: actions/checkout@v7 - uses: luizm/action-sh-checker@v0.10.0 with: sh_checker_exclude: 'scripts' sh_checker_checkbashisms_enable: true
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 useslatchkey-small; pick the runner size that fits the job. - 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.