If a pinto project leverages a cloned conda environment, and that base environment gets updated, running pinto build won't pickup any of the changes to the base environment in the new one. We could include a --fresh kwarg (or something similar), that completely deletes the existing environment and rebuilds it from scratch. One question for this might be: does it delete the base environment too, and rebuild that from any changes to the base environment.yaml?
If a pinto project leverages a cloned conda environment, and that base environment gets updated, running
pinto buildwon't pickup any of the changes to the base environment in the new one. We could include a--freshkwarg (or something similar), that completely deletes the existing environment and rebuilds it from scratch. One question for this might be: does it delete the base environment too, and rebuild that from any changes to the baseenvironment.yaml?