Commit Graph
3 Commits
Author SHA1 Message Date
ari d47c401013 hooks + devenv 2026-09-17 14:14:14 -04:00
ari b1c6a52503 hooks + devenv 2026-09-17 13:18:19 -04:00
ariandClaude Sonnet 5 825094c4cf Commit flake.lock; keep --no-write-lock-file as a defensive fallback
Fixes "cannot write modified lock file" when running hermenix straight
from its git+ssh URL (no local checkout) - Nix had nothing committed to
resolve its own sub-inputs (nixos-generators, determinate, nixpkgs)
against, and can't write one back to a fetched, read-only copy. A
committed, current flake.lock means there's nothing left to resolve on
a normal run.

Also finished threading --no-write-lock-file through the two remaining
CLI-constructed invocations (setup's printed manual-fallback text, and
remote's constructed command) that were missed in the prior commit -
harmless once the lock is current, and keeps things working even if the
lock ever drifts stale before it's refreshed.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-09-15 15:38:49 -04:00