shcheklein
commented
2 years ago but you need to clone example-repos-dev, which is another repo
this repo is not meant to be used by users / readers. This repo is done for us to help us maintain tutorials / example repos. E.g. if I want to change something in the middle of the example repo history, update tools, updates all .dvc files in the history to the newer version, etc - this repo help a lot with this.
In case of GTO this repo could be used to generate the self-contained example repo and then text tutorial can show users what do with it. Essentially this repo is for us to help us maintain and keep up to date the self-contained example repo in this case.
Or it can be that you decide to all the steps for users and make it the final result - that's also fine, our docs are written in way that users can take the final repo result if they want, but they could also go thought the process from the very beginning (git init, dvc init, add code, etc) or from a tag in the middle (and we provide the list of tags).
aguschin
Ok, I created PR to
example-repos-dev, but in the process I think we losed the great way for users to regenerate the repo themselves (this is mode important compared to DVC or MLEM). Earlier it was like this: fork, clone, checkout to dev, run bash script. Now you can also do that, but you need to cloneexample-repos-dev, which is another repo, and then monkeypatchgenerate.sh, then deal withghand etc. It's acceptable for us, but not so easy for users. I will consider creating self-contained example repo which could be used in old scenarios.