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. :shrug:
MattF-NSIDC
commented
1 year ago
The CryoCloud hub-image project uses/used a
/condalockcommand 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. :shrug: