-
Notifications
You must be signed in to change notification settings - Fork 341
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs: repo_token
=> REPO_TOKEN
#492
Conversation
Please note that we currently have our documentation spread over a few places; you may also want to update https://cml.dev (source) and https://dvc.org/doc/cml (source). |
Wait what. https://dvc.org/doc/cml is just a mirror of this repo's README. Much duplication such inefficient. @jorgeorpinel @shcheklein any better suggestions? I'd really rather prefer dvc.org/doc/cml to be a one page blurb containing links to this repo & cml.dev |
I'm inclined to think that it would be better to keep documentation in a single place (preferably cml.dev) and point to it from both dvc.org/doc/cml and the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
https://dvc.org/doc/cml is just a mirror of this repo's README. Much duplication such inefficient. @jorgeorpinel @shcheklein any better suggestions? I'd really rather prefer dvc.org/doc/cml to be a one page blurb containing links to this repo & cml.dev
Yeah I think the README existed first and was the main documentation. At some point we needed to publish CML docs somewhere formal for some reason so it was copied over. Definitely should not have the same content. The Q is what's the vocation of each one? README vs CML docs (home page), that is.
Same Q applies for DVC BTW... @casperdcl do you want to make an issue about the product READMEs in the docs repo?
Sure @jorgeorpinel I just opened iterative/dvc.org#2443 which is going to be fun :) |
Follow-up to #489