-
Notifications
You must be signed in to change notification settings - Fork 394
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
fetch: review sample command output #551
Comments
The effort for this may be too great. Perhaps we should rather think of a way that will be sustainable in the future to make sure all our code and console examples remain valid as DVC changes. For example generating them all from scripts in a separate |
I would just create a small tickets from time to time to update it. I don't think we need a special machinery around this. At least now. Too much effort. |
As part of this one, I would just grep "{scheme ...}" messages and replace them with human readable versions. It should be straightforward and should not require running all these examples, I hope. |
was just an example. I meant absolutely all the ```dvc code block examples, basically. There's 450 :/ |
Yep, I +1 on that it's too much of a scope to update them. But also I'm not sure we need some very specific mechanism to keep them up-to-date. At least for now. Let's just do the best we can when we update docs. |
Fair enough! Hopefully we can count on users reporting any problems via issues. |
I meant - let's open this particular one open :) Just fix fetch examples. And may be similar outputs around. |
Closing as dupe of #614 (comment). |
For example from static/docs/commands-reference/fetch.md line 204+:
The text was updated successfully, but these errors were encountered: