igordertigor

Thank you @aguschin for your quick reply. Here are a few thoughts: 1. I looked at the section you linked about private repositories and added the option to set GITHUB_TOKEN...

> 5. I guess the best bet here would be to adapt DVC's approach https://github.com/iterative/dvc/blob/main/dvc/external_repo.py . This should require implementing something on top of [`CloudGitResolver`](https://github.com/iterative/mlem/blob/main/mlem/core/meta_io.py) which will work for any...

Hi @aguschin, here is my `.mlem.yaml`: ``` $ cat .mlem.yaml core: storage: type: dvc ``` Regarding your second question: I tried with and without DVC installed and with and without...

Is this answering your question: ``` $ head models/my-model.mlem artifacts: data.pkl: hash: f47d01924e75f480b416338e313b3812 size: 5759 type: dvc uri: my-model model_type: io: type: pickle methods: ``` Similar for the other one....

I don't think that's it. The repository is private, but I'm getting the same issue locally, if I just create a new virtual env/repository and everything. However, I am locally...

Hi @aguschin , apologies for the late reply. I've been away from my computer for a couple of days and will likely be here sporadically in the next couple of...

Thanks @aguschin , I think those are pretty much the issues I'm facing. Any idea why it doesn't work for ssh connections? After all, I can `dvc get` with the...

This is about missing documentation, not about the accept always behavior itself. Hence the above github-actions comments do not apply.

Thank you! That's very useful. Will that become part of the documentation at some point?

I'm happy to add it if you need help.