Check UN Geodata Updates workflow (plotly/plotly.js)

The Check UN Geodata Updates workflow from plotly/plotly.js, explained and optimized by Latchkey.

What it does

This is the Check UN Geodata Updates workflow from the plotly/plotly.js 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 UN Geodata Updates

on:
  schedule:
    # First day of every month at 09:00 UTC
    - cron: '0 9 1 * *'
  workflow_dispatch:

permissions:
  issues: write

jobs:
  check-geodata:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6
        with:
          sparse-checkout: .github/scripts

      - name: Check for UN Geodata updates
        uses: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea # v7
        with:
          script: |
            const { default: checkUnGeodata } = await import('${{ github.workspace }}/.github/scripts/check-un-geodata.mjs');
            await checkUnGeodata({ github, context, core });

The same workflow, on Latchkey

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

name: Check UN Geodata Updates
 
on:
  schedule:
    # First day of every month at 09:00 UTC
    - cron: '0 9 1 * *'
  workflow_dispatch:
 
permissions:
  issues: write
 
jobs:
  check-geodata:
    timeout-minutes: 30
    runs-on: latchkey-small
    steps:
      - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6
        with:
          sparse-checkout: .github/scripts
 
      - name: Check for UN Geodata updates
        uses: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea # v7
        with:
          script: |
            const { default: checkUnGeodata } = await import('${{ github.workspace }}/.github/scripts/check-un-geodata.mjs');
            await checkUnGeodata({ github, context, core });
 

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

Actions used in this workflow