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

Support --repo, --no-repo, and autoinit in dstack apply #2080

Merged
merged 4 commits into from
Dec 12, 2024

Conversation

r4victor
Copy link
Collaborator

Closes #2072

This PR improves the repos and dstack apply UX:

  • Allows specifying a repo for the run via -P/--repo. The repo can be a local path or a remote Git repo URL. Previously, dstack always used the current directory as a repo and required it to be initialized.
  • If the repo is specified but not initialized, dstack apply will init the repo. dstack apply accepts the same parameters as dstack init to init the repo. This is primarily useful when working with remote repos without cloning them locally.
  • Allows specifying --no-repo if no repo is needed for the run. In this case, the run repo directory (/workflow) will be empty.

If the repo is not specified, dstack apply requires the directory to be initialized as before.

@r4victor r4victor requested review from jvstme and un-def December 11, 2024 10:51
@r4victor r4victor merged commit a412138 into master Dec 12, 2024
23 checks passed
@r4victor r4victor deleted the issue_2072_dstack_apply_repo branch December 12, 2024 03:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Support repo autoinit and remote repos without cloning in dstack apply
2 participants