Without pixi --update, --carryover-lockfile can cause broken pixi state. IIUC, pixi --update "fixes" lockfiles which may be "mostly" correct (as those injected by --carryover-lockfile are), and is also much faster than --install.
Speaking of --install, let's make the default here --no-install, so that we can avoid actually pulling any packages unless we are really running tests etc. (In cases of just committing recompiled changes, we don't need to burn that network time.)
Without
pixi --update
,--carryover-lockfile
can cause broken pixi state. IIUC,pixi --update
"fixes" lockfiles which may be "mostly" correct (as those injected by--carryover-lockfile
are), and is also much faster than--install
.Speaking of
--install
, let's make the default here--no-install
, so that we can avoid actually pulling any packages unless we are really running tests etc. (In cases of just committing recompiled changes, we don't need to burn that network time.)Note that no-install may involve taking a look at https://github.com/prefix-dev/pixi/issues/817, since we do have
https://github.com/wildlife-dynamics/ecoscope-workflows/blob/3887263264e16809337b23e5d0ba11f72f8c23af/examples/patrols/ecoscope-workflows-patrols-workflow/pixi.toml#L65-L67
but I think we can exchange that block for perhaps just like, a sys.path addition or something 🤔