Support --repo, --no-repo, and autoinit in dstack apply #2080
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #2072
This PR improves the repos and
dstack apply
UX:-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.dstack apply
will init the repo.dstack apply
accepts the same parameters asdstack init
to init the repo. This is primarily useful when working with remote repos without cloning them locally.--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.