From 2a0ed69d0dcb2e63d367f0263912df0d98d45e09 Mon Sep 17 00:00:00 2001 From: Ben Dichter Date: Fri, 21 Aug 2026 12:36:32 -0400 Subject: [PATCH] Fix index workflow: schedule belongs under on, not concurrency The concurrency block added in #195 was inserted before the existing schedule trigger, which left schedule nested under concurrency. The file stayed valid YAML, so the pre-merge check passed, but GitHub rejects it as an invalid workflow, and every index run since has failed before creating a job. The live site has therefore been stale since then. Validated with actionlint. Co-Authored-By: Claude Fable 5 --- .github/workflows/index_workflow.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/.github/workflows/index_workflow.yml b/.github/workflows/index_workflow.yml index 3e07e2c..d35c56d 100644 --- a/.github/workflows/index_workflow.yml +++ b/.github/workflows/index_workflow.yml @@ -9,13 +9,13 @@ on: workflow_run: workflows: ["Build notebook images"] types: [completed] + schedule: + - cron: '30 6 * * 1' # weekly, after the notebook test sweep, to refresh docker badges # Deploys push to the same gh-pages branch; never run two at once. concurrency: group: index-deploy cancel-in-progress: false - schedule: - - cron: '30 6 * * 1' # weekly, after the notebook test sweep, to refresh docker badges jobs: collect-and-render: