From c9efbc3ce597ee20de52bcb0e7def855c16d8dd4 Mon Sep 17 00:00:00 2001 From: SoundMindsAI Date: Tue, 16 Jun 2026 15:55:40 -0400 Subject: [PATCH] chore(ci): daily cron for deploy-docs to keep relyloop.com stamp fresh MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Add a `schedule:` trigger (daily 03:17 UTC) to deploy-docs.yml so the relyloop.com footer's "build SHA / merged PR / built X ago" stamp auto-refreshes regardless of which paths the day's PRs touched. Why. The existing trigger fires only when something under `website/**` or the workflow file itself changes. This is correct for content freshness — the public site genuinely only changes when its sources change — but it leaves the build stamp pinned at the last website-touching merge. After a week of active infra/chore PRs (like the 12 corp-network install story PRs that landed today, none of which touched `website/`), a reader visiting relyloop.com sees an apparent week-old build and thinks the project is stale, even though main has advanced ~30 commits. The rebuild itself is a no-op when nothing in website/ has changed — the generated site bytes are identical; only the stamp's SHA / PR / timestamp refresh in the footer. Timing rationale. 03:17 UTC is offset from the existing project crons (codeql 04:31 Mon, scorecard 04:27 Mon, reconcile-tracking-issues 05:17 daily) for the project's "minute 17" convention and to avoid GHA peak- load windows. The deploy uses concurrency group "pages" so timing collisions with other workflows don't matter — they'd serialize. Cost. ~30s of GHA time per day = negligible. The workflow already runs on every website/ change, so we're not introducing new infrastructure; just a more frequent trigger of an already-validated workflow. Companion action: triggered the workflow once manually via `gh workflow run deploy-docs.yml --ref main` to refresh the stamp immediately (run 27644073762), so the site reflects today's main (69201065 / #528) before the first cron fires tomorrow at 03:17 UTC. Co-Authored-By: Claude Opus 4.7 Signed-off-by: SoundMindsAI --- .github/workflows/deploy-docs.yml | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/.github/workflows/deploy-docs.yml b/.github/workflows/deploy-docs.yml index f000cb57..7c47b154 100644 --- a/.github/workflows/deploy-docs.yml +++ b/.github/workflows/deploy-docs.yml @@ -10,6 +10,18 @@ on: paths: - "website/**" - ".github/workflows/deploy-docs.yml" + # Daily rebuild keeps the relyloop.com footer's "build SHA / merged PR / + # built X ago" stamp current. Without this, infra / chore / docs PRs that + # don't touch website/** leave the stamp pinned at the last website- + # touching merge — so a reader visiting the site after a week of active + # work sees an apparent week-old build and thinks the project is stale. + # The rebuild is a no-op when nothing in website/ has changed (same + # generated site bytes; only the stamp's SHA / PR / timestamp refresh). + # 03:17 UTC is offset from the existing project crons (codeql 04:31 Mon, + # scorecard 04:27 Mon, reconcile-tracking-issues 05:17 daily) — both for + # the "minute 17" convention and to avoid hitting GHA peak-load windows. + schedule: + - cron: "17 3 * * *" workflow_dispatch: # Least privilege for GitHub Pages deployment.