Currently, you can use DagsHub to create a repo in 2 ways:
- CLI
- Python API
Each one doesn't have all the options, which creates a strange UX when they are necessary.
The CLI flow, doesn't have the option to create a private repo, but does enable cloning the repo locally after creating it. The Python API does have the visibility option, but not the cloning option.
It would be good to have either the CLI or the API have all options. This can be achieved either by adding a clone flag to the Python function, and moving the logic for cloning from the CLI to the API, and/or we can add a --private flag to the CLI command that uses the argument in the API to create a private repo
Currently, you can use DagsHub to create a repo in 2 ways:
Each one doesn't have all the options, which creates a strange UX when they are necessary.
The CLI flow, doesn't have the option to create a private repo, but does enable cloning the repo locally after creating it. The Python API does have the visibility option, but not the cloning option.
It would be good to have either the CLI or the API have all options. This can be achieved either by adding a clone flag to the Python function, and moving the logic for cloning from the CLI to the API, and/or we can add a
--privateflag to the CLI command that uses the argument in the API to create a private repo