ci(cachix): write to the cache on every push, read it in every job that runs nix

The write token goes to cachix-action on a push (master and the temporary komomono
trigger, without naming either), a manual run and a schedule; a pull request, a fork
and the merge queue only read. The flake-lock update goes through the nix action too,
and the nixpkgs canary reads the cache but never pushes (push: "false" replaces
cache: "false").

docs(ci): the write rule, the read-only path and a checklist for the first push to
komomono.
This commit is contained in:
LGUG2Z committed 2026-11-05 16:40:29 -08:00
1 parent 17fb726ecf
commit 166e5f353a
4 files changed
+35 -16

No files matched your search

+1 -2
View File
@@ -133,10 +133,9 @@ jobs:
- uses: ./.github/actions/nix
with:
kvm: "true"
cache: "false"
push: "false"
swap: "true"
cachix-cache: ${{ vars.CACHIX_CACHE }}
cachix-auth-token: ${{ secrets.CACHIX_AUTH_TOKEN }}
- name: Move nixpkgs to the tip in a copy of the checkout
run: |
cp -a . "$RUNNER_TEMP/canary"
+4 -1
View File
@@ -19,7 +19,10 @@ jobs:
pull-requests: write
steps:
- uses: actions/checkout@v6
- uses: cachix/install-nix-action@v31
- uses: ./.github/actions/nix
with:
cachix-cache: ${{ vars.CACHIX_CACHE }}
cachix-auth-token: ${{ secrets.CACHIX_AUTH_TOKEN }}
- uses: DeterminateSystems/update-flake-lock@v29
with:
commit-msg: "chore(deps): flake.lock: Update"