- queue: max on every data-write workflow (GitHub, 2026-05-07): up to 100 runs wait, first in, first out. The default kept one, and a run queueing behind a running job cancelled it. - ref: main on every checkout. A run's commit is fixed when it is created, so a run that waited behind another data job wrote shards from before that job's commit; Auto Update JSON failed four days in ten on the rebase conflict in data/index.json. - timeout-minutes everywhere, and JOB_BUDGET_MINUTES at least 20 below it for the long loops (never for the ingest, which empties its queue). - pipeline.test.ts fails on a data-write workflow missing any of these. - The admin's Pipeline and Automation pages, docs/ADMIN.md and the auto-approve comment no longer say a push evicts a waiting job; the idle gate stays, so a batch's ingest starts at once. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
26 lines
852 B
YAML
26 lines
852 B
YAML
name: Daily Snapshot
|
|
on:
|
|
schedule: [{cron: '0 23 * * *'}]
|
|
workflow_dispatch:
|
|
permissions: {contents: write}
|
|
# Shares the data-write group with every other workflow that commits to
|
|
# data/ — without it this can push mid-run against a long job. queue: max -
|
|
# a run that finds another data job running waits its turn (first in, first
|
|
# out) instead of evicting the run already waiting.
|
|
concurrency:
|
|
group: data-write
|
|
cancel-in-progress: false
|
|
queue: max
|
|
jobs:
|
|
snapshot:
|
|
runs-on: ubuntu-latest
|
|
timeout-minutes: 20
|
|
steps:
|
|
# main as it is when the job STARTS, so the snapshot holds what the
|
|
# jobs before it committed.
|
|
- uses: actions/checkout@v4
|
|
with: {ref: main}
|
|
- uses: actions/setup-python@v5
|
|
with: {python-version: '3.15'}
|
|
- run: chmod +x ./bash/snapshot.sh && ./bash/snapshot.sh
|