cmd ref: update `import`: it now supports non-DVC Git repos

[jorgeorpinel]

Per treeverse/dvc/pull/3020.

See treeverse/dvc#3020 (comment), treeverse/dvc#3020 (comment), and treeverse/dvc#3020 (comment):

Regarding documentation, I could edit https://github.com/iterative/dvc.org/blob/master/static/docs/command-reference/import.md and change "DVC repository" to "DVC or Git repository" but I'm not sure if that's really necessary.

• sounds like a good first step but I imagine there needs to be more changes, would have to read the cmd ref thoroughly and think about it. Please open the PR and we'll get that review process stated.

• Regarding docs, sure we need to note that this now works on non-dvc repos, there is no doubt about it and it is clearly necessary. 🙂

• Yes I think docs definitely need to be updated so that the dvc import command reference reflects the changes in this PR. You can open a separate iterative/PR on dvc.org for that and we'll review it there and help finish it if necessary. Thanks for the heads up, guys.

UPDATE: Perhaps the only thing missing is to add an example specific to importing Git-tracked file. See #898 (comment)

[utkarshsingh99]

It seems this issue has been solved by a PR that may not have mentioned this issue.
The import.md page in command-reference mentions this:

Download a file or directory tracked by DVC or by Git into the workspace. It also creates a DVC-file with information about the data source, which can later be used to update the import.

In case if it needs to be more explicitly stated 'non-DVC Git repos', I'll be happy to take this up

[jorgeorpinel]

@utkarshsingh99 thanks! Indeed this is now included in https://dvc.org/doc/command-reference/import but perhaps

• the only thing missing is to add an example specific to importing Git-tracked files.

You can try this if you wish.

[utkarshsingh99]

Sure, I will look into it.