Add slash command /condalock to autogenerate conda-lock files #5
Conversation
To enable easier reproducibility of conda environments, create an automated way of refreshing conda-lock files by writing `/condalock` as as slash command in Pull Request comments. Also briefly documented all the GitHub Actions workflows in `.github/workflows/README.md`.
|
|
|
@yuvipanda, I've just created a After that, we'll need to set the |
|
@weiji14 you should have access now! |
|
Cool, thanks Yuvi! Let me do some testing to see if it works. |
weiji14
force-pushed
the
slash-command-condalock
branch
from
7558169
to
11a5e62
Compare
Let the `git ls-files` pick up new files (like `conda-linux-64.lock`) too. Also changed command-line arguments to long-form for better readability.
To be updated by the condalock slash command later.
|
Yay, it works! Tested this on a personal fork (since the workflow needs to be tested with the GitHub Actions files being already on the main branch). So I wrote the |
|
@weiji14 great! Wanna merge and test? |
|
Sure! Right now this is only generating the 'old' explicit lockfile from |
Update instructions on how to add or update dependencies in the cryocloud docker image. Specifically, documenting the `/condalock` slash command added in #5 which runs [`conda-lock`](https://github.com/conda-incubator/conda-lock) for creating snapshots of fully reproducible conda environments.
To enable easier reproducibility of conda environments, create an automated way of refreshing conda-lock files by writing
/condalockas as slash command in Pull Request comments.Related to CryoInTheCloud/CryoCloudWebsite#1 (comment)
Based on:
TODO setup auth tokens for automated commits, based on GenericMappingTools/pygmt#646 (comment)
CryoInTheCloudGitHub App to generate tokens, followingcryointhecloud-botin this repositoryAPP_IDandAPP_PRIVATE_KEYas secrets to the repo