Continuing discussion on whether to move some of the conda-lock related automation into a standalone GitHub Actions Continuous Integration workflow that can be shared with https://github.com/pangeo-data/pangeo-docker-images or other people.

@weiji14 how do you feel about extracting the conda-lock stuff from here into an action by itself? Then we can use that action in pangeo-docker-images, thus removing duplicate work...

Originally posted by @yuvipanda in #13 (comment)

To be clear, do we mean:

• The /condalock command added in Add slash command /condalock to autogenerate conda-lock files #5, which I think pangeo-docker-images has a version of already maintained by @scottyhq?
• The 'installing from conda-lock.yml' script being worked on at Using unified conda-lock file in postBuild for reproducible conda environment #14? A quick search led to conda-incubator/setup-miniconda fails when using conda-lock.yml conda/conda-lock#245 (comment) and apparently there might be something re-usable already at https://github.com/mamba-org/provision-with-micromamba#example-with-customization?