From d696567fc8ac0a7f5fc8c40f6654f2fd78307e31 Mon Sep 17 00:00:00 2001
From: foxnne <foxnne@gmail.com>
Date: Thu, 8 Oct 2026 09:34:20 -0500
Subject: [PATCH] ci: a push to main runs the full matrix, so main holds every
 cache

A pull request restores its Zig caches from its own earlier runs or from main's; a cache a pull
request saves is visible to that pull request alone. A push to main ran only the Linux jobs, so
main never held a macOS, Windows or cross-build cache and every pull request's first run built
those three cold (#233's warm runs took 43 s, 285 s and 50 s against 389 s, 501 s and 365 s
cold).

A push to main now runs what a pull request runs: the three-platform test matrix and the Windows
cross-build. The merge that changes a dependency saves the new caches under main, a cache GitHub
evicts after a quiet week comes back on the next merge, and every merge is tested on all three
platforms. Nothing waits on a main run, and with a cache hit the extra jobs are short.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---
 .github/workflows/ci.yml | 19 +++++++++++++++----
 1 file changed, 15 insertions(+), 4 deletions(-)

diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml
index b95c8f906..55cfc0195 100644
--- a/.github/workflows/ci.yml
+++ b/.github/workflows/ci.yml
@@ -1,12 +1,20 @@
 name: CI
 
-# PR / merge queue / manual: three native test jobs (no skipped rows). Push to main: Linux-only
-# (fast).
+# Every run, a push to main included: three native test jobs (no skipped rows) and the Windows
+# cross-build.
 #
 # `ci-ok` is the one check `main`'s ruleset requires (`.github/rulesets/main.json`), so the
 # workflow runs for every change. A workflow-level `paths-ignore` would never start for a
 # Markdown-only PR, leaving its required check waiting for good; `changes` works out instead
 # whether anything besides docs changed, and the builds skip themselves when nothing did.
+#
+# A push to main runs the full matrix because main's runs are the only ones whose Zig caches
+# every pull request can restore: a cache a pull request saves is visible to that pull request
+# alone (see the test job's "Restore Zig cache"). Pushes used to run only the Linux jobs, so main
+# held no macOS, Windows or cross-build cache and every pull request's first run built those
+# three cold. Now the merge that changes a dependency saves the new caches, a cache GitHub
+# evicted after a quiet week comes back on the next merge, and every merge is tested on all
+# three platforms. Nothing waits on a main run, and a cache hit makes the extra jobs short.
 on:
   push:
     branches: [main]
@@ -72,7 +80,10 @@ jobs:
     strategy:
       fail-fast: false
       matrix:
-        include: ${{ github.event_name == 'push' && fromJSON('[{"os":"ubuntu-latest","name":"Linux"}]') || fromJSON('[{"os":"ubuntu-latest","name":"Linux"},{"os":"windows-latest","name":"Windows"},{"os":"macos-14","name":"macOS"}]') }}
+        include:
+          - { os: ubuntu-latest, name: Linux }
+          - { os: windows-latest, name: Windows }
+          - { os: macos-14, name: macOS }
     runs-on: ${{ matrix.os }}
     steps:
       - uses: actions/checkout@v4
@@ -222,7 +233,7 @@ jobs:
   windows-fizzy-backend:
     name: Windows build (fizzy backend, cross-compiled)
     needs: changes
-    if: github.event_name != 'push' && needs.changes.outputs.code == 'true'
+    if: needs.changes.outputs.code == 'true'
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v4