skshetry

The `datasets` section implemented in this PR is as a list in `dvc.yaml`. `metrics`/`params`/`plots` are also a list. But the `artifacts` section is a dictionary, which has a similar schema/format...

> > $ dvc ds add dvc://[email protected]:iterative/example-get-started.git@main#path=data/data.xml I am not against supporting this. But I find this url to be very complex, and I doubt if I'll remember it when...

> Yup, it might be worse, especially if you think we should keep --path and --rev. Do you think we should revert to using --type then? Is `--url dvc://[email protected]:iterative/example-get-started.git` worse...

I'll disable non-cloud-versioned remotes/filesystems in the successive PRs.

> Can you drop them from the parser help text in this PR? I was focused on that more than actually disabling them. I have dropped them from the help...

I think this will be part of #5369. Closing in favor of that.

Could you please provide more information? Is that above error message from dvc? If it is, could you please also include verbose output from dvc?

I don't think there is anything for us to do here. As Peter mentioned, it's okay to do a `git gc``/git prune` and is the correct fix/suggestion. Closing.

yeah, I don't understand it as well. We are looking for a way to make it DRY, and less repeatable. Think of cases where the stages are already created with...

I am planning on working on this, this week.