Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider adding a GitHub action which locks config and environment #593

Open
MattF-NSIDC opened this issue Jun 29, 2023 · 1 comment
Open

Comments

@MattF-NSIDC
Copy link

The CryoCloud hub-image project uses/used a /condalock command you'd post in a PR comment to trigger an action to lock the environment and add a commit to the PR. We could do similar. Or we could have a different way of triggering it. I think when a commit is being added by an automation, it should be triggered by a human so the human is not surprised by a new commit on the remote.

In any case, I think it will be helpful to have this type of escape hatch for new contributors who don't know about our config locking mechanisms and don't really have a good reason to care. We can edit the PR template to tell people if you have any errors about X, post "Y" as a comment in this PR to resolve. 🤷

@MattF-NSIDC
Copy link
Author

conda/conda-lock#479

@MattF-NSIDC MattF-NSIDC moved this to 🔖 Ready in QGreenland Aug 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: 🔖 Ready
Development

No branches or pull requests

1 participant