Skip to content

cmd ref: get and import are getting confusing #920

@jorgeorpinel

Description

@jorgeorpinel

WARNING: RANTish

#912 will soon merge the updates to the behavior of dvc get and dvc import, which now completely support dealing with regular Git repos (no DVC involved at all).

I forget what was the reason to implement that on the core repo but I'm sure there were good motives, however, it's made them confusing or at least difficult to explain.

We should probably revisit the command references again and explain again:

  • Focus mostly on the DVC-related features and
  • only note somewhere about regular Git repo support.

This way we'll avoid confusing phrases and paragraphs like `url` (location which can be a path) and `path` (also location) (both HTTPS or SSH supported) to DVC project (which can be a DVC repo, which is a Git repo) or Git repo (we mean a plain repo without DVC inside) ... – exagerated.

Metadata

Metadata

Assignees

No one assigned

    Labels

    A: docsArea: user documentation (gatsby-theme-iterative)C: refContent of /doc/*-referencestatus: researchWriting concrete steps for the issuetype: enhancementSomething is not clear, small updates, improvement suggestions

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions