-
Notifications
You must be signed in to change notification settings - Fork 4
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
include clone commands in setup steps #62
Conversation
Alternative to #61 that's a little more general |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, that's helpful. We should remove the private repo error (or change it to a warning or something)
Done: f1ca461 |
'git clone "${REPO_URL}" .', | ||
'git checkout "${GIT_REF}"', | ||
"git submodule update --init --recursive", | ||
"conda shell.bash activate base", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like we do expect conda. If so, can we just define PRIVATE_REPO_SETUP_STEPS
, and then it will Just Work ™ ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But this is just the default because we know conda will be on the default images.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, fair enough.
No description provided.