Hatch caches data on behalf of the user. This idea came up when discussing environments created as part of hatch run <script>. I don't know if there is other cached data that could benefit from this command, but the following could be useful for managing script environments.
This list is a bit "off the top of my head" - I can think of use cases for all of these, but there may be other possibilities as well, or there may be better ways of structuring the subcommands.
hatch cache dir - print the location of the cache directory.
hatch cache prune - remove cached environments that relate to scripts that no longer exist on disk.
hatch cache purge - remove all cached environments, forcing them to be recreated when next needed.
hatch cache find <script> - print the location of the environment directory for Githubissues.
Githubissues is a development platform for aggregating issues.
Hatch caches data on behalf of the user. This idea came up when discussing environments created as part of
hatch run <script>. I don't know if there is other cached data that could benefit from this command, but the following could be useful for managing script environments.This list is a bit "off the top of my head" - I can think of use cases for all of these, but there may be other possibilities as well, or there may be better ways of structuring the subcommands.
hatch cache dir- print the location of the cache directory.hatch cache prune- remove cached environments that relate to scripts that no longer exist on disk.hatch cache purge- remove all cached environments, forcing them to be recreated when next needed.hatch cache find <script>- print the location of the environment directory for Githubissues.