You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit d44aeda
Browse filesBrowse the repository at this point in the historyBrowse files
ci: decide in ci.yaml that only main persists caches
The Nix sticky disks are keyed by job, not by ref, so pull request and
merge group runs mount the same disk main commits and release builds
read. What keeps their changes out of it is the stickydisk `commit` flag,
and setup-nix-cache derived that flag on its own from the ref. A
merge_group run checks out the queued commit, so that local action is the
queued code's own copy, and nothing in ci.yaml stated the rule.
ci.yaml now sets PERSIST_CACHES from `github.ref == 'refs/heads/main'` and
passes it to every Nix store and Cargo cache save. Non-main runs still
mount main's warm disk, so pull requests keep their cache hits, but they
mount it without committing and the clone is discarded.
This cannot stop a queued commit that edits ci.yaml itself; review before
queuing is that boundary. It stops a change to a local action, or an
unreviewed-code path, from writing a store that main reads.
0 commit comments