Check updated RELEASES.md file workflow (PythonOT/POT)

The Check updated RELEASES.md file workflow from PythonOT/POT, explained and optimized by Latchkey.

What it does

This is the Check updated RELEASES.md file workflow from the PythonOT/POT 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: "Check updated RELEASES.md file"

on:
  pull_request:
    branches:
      - 'master'
jobs:
  check_release_file:
    permissions:
      contents: read
      pull-requests: write
    runs-on: ubuntu-latest
    steps:
      - name: Verify Changed files
        uses: tj-actions/changed-files@v45
        id: changed-release-file
        with:
          files: 'RELEASES.md'
      - name: Check if RELEASES.md file is changed
        if: steps.changed-release-file.outputs.any_changed == 'false'
        run: exit 1

The same workflow, on Latchkey

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

name: "Check updated RELEASES.md file"
 
on:
  pull_request:
    branches:
      - 'master'
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true
 
jobs:
  check_release_file:
    timeout-minutes: 30
    permissions:
      contents: read
      pull-requests: write
    runs-on: latchkey-small
    steps:
      - name: Verify Changed files
        uses: tj-actions/changed-files@v45
        id: changed-release-file
        with:
          files: 'RELEASES.md'
      - name: Check if RELEASES.md file is changed
        if: steps.changed-release-file.outputs.any_changed == 'false'
        run: exit 1
 

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.
• 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