Github Release Publish workflow (jorisroovers/gitlint)

The Github Release Publish workflow from jorisroovers/gitlint, explained and optimized by Latchkey.

What it does

This is the Github Release Publish workflow from the jorisroovers/gitlint 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: Github Release Publish
run-name: "Github Release Publish (tag=${{github.ref_name}})"

on:
  release:
    types: [published]

jobs:
  publish-release:
    uses: ./.github/workflows/publish-release.yml
    secrets: inherit # pass all secrets (required to access secrets in a called workflow)
    with:
      pypi_target: "pypi.org"
      repo_release_ref: ${{ github.ref_name }} 
      docker_image_tag: "Use $gitlint_version"

The same workflow, on Latchkey

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

name: Github Release Publish
run-name: "Github Release Publish (tag=${{github.ref_name}})"
 
on:
  release:
    types: [published]
 
jobs:
  publish-release:
    timeout-minutes: 30
    uses: ./.github/workflows/publish-release.yml
    secrets: inherit # pass all secrets (required to access secrets in a called workflow)
    with:
      pypi_target: "pypi.org"
      repo_release_ref: ${{ github.ref_name }} 
      docker_image_tag: "Use $gitlint_version"
 

What changed

• Add a job timeout so a hung step cannot burn hours of runner time.

This workflow runs 1 job per trigger. On Latchkey the same minutes cost up to 58% less than GitHub-hosted, with zero queue time.