Repository navigation
Daily schedule for the publish/export workflow - #56
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a daily
scheduletrigger (andworkflow_dispatch) topublish.yml, so exports and archive snapshots refresh every day rather than only when a commit touchesincidents//schema//scripts/.Why
publish.ymlwaspush-only, so thechore(export): refresh exportscommits appeared only on days with an incident push. A daily run also keeps archive.org snapshots current (viacheck_links.py --backfill), which can change exports even with no new incidents.Safety
No job-body change is needed — the workflow is already timer-safe:
reset --hards toorigin/mainand rebuilds exports from scratch; it never relies on the push's changed-paths diff, so a scheduled run behaves identically to a push run.git diff --cached --quiet -> "nothing to publish"; return 0guard makes a no-change day a clean success — no empty commit, no failure.[skip ci]on the export commit still prevents self-triggering loops.Cron is
0 7 * * *(07:00 UTC), offset from the weekly jobs at 09:00/10:00 UTC.