Skip to content
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: List instances of stage file concepts, dvc run/checkout/repro for example review and update to 1.0 #1743

Closed
31 of 37 tasks
jeremydesroches opened this issue Aug 31, 2020 · 17 comments
Labels
A: docs Area: user documentation (gatsby-theme-iterative) ✨ epic Placeholder ticket for multi-sprint direction, use story, improvement type: enhancement Something is not clear, small updates, improvement suggestions

Comments

@jeremydesroches
Copy link
Contributor

jeremydesroches commented Aug 31, 2020

From #1255 :

Create a list of places where the concept of stage file(s) and dvc run/checkout/repro are used...

List of places here, including initial example:

Get Started

User Guide

Use Cases

Install

Command Reference

Second part from #1255, which may be better as second issue:

We should review all those docs to make sure the use of dvc run/etc and YAML examples are updated to 1.0.

(Items in list above will be checked when checked/updated.)

@jeremydesroches jeremydesroches added the A: docs Area: user documentation (gatsby-theme-iterative) label Aug 31, 2020
@jeremydesroches jeremydesroches self-assigned this Aug 31, 2020
@jeremydesroches jeremydesroches changed the title docs: List instances of stage file concepts, dvc run/checkout/repro for example review/updating to 1.0 docs: List instances of stage file concepts, dvc run/checkout/repro for example review and updates to 1.0 Aug 31, 2020
@jeremydesroches jeremydesroches changed the title docs: List instances of stage file concepts, dvc run/checkout/repro for example review and updates to 1.0 docs: List instances of stage file concepts, dvc run/checkout/repro for example review and update to 1.0 Aug 31, 2020
@jeremydesroches
Copy link
Contributor Author

jeremydesroches commented Aug 31, 2020

@jorgeorpinel I'll list the issues as shown. Should the second part remain here or be its own issue?

@jorgeorpinel
Copy link
Contributor

Nice, thanks @jeremydesroches. Let's keep the 2nd part here for now. I edited the description above a bit.

@jorgeorpinel
Copy link
Contributor

jorgeorpinel commented Sep 13, 2020

Hey @jeremydesroches I see (almost) all the check boxes are marked now, but only a few are addressed in PR #1766. Can you explain what happened? Thanks

@jeremydesroches
Copy link
Contributor Author

jeremydesroches commented Sep 13, 2020

Yes, I reviewed all the items in the list and marked them as follows:

@jorgeorpinel
Copy link
Contributor

Got it. Glad to see most of it is done then. Are you planning to finish this one off then? Or would you rather turn to SEO work at this point?

@jeremydesroches
Copy link
Contributor Author

jeremydesroches commented Sep 13, 2020 via email

@jorgeorpinel
Copy link
Contributor

OK. Also the 2nd part may be pending (dvc run/repro and YAML examples).

@jorgeorpinel
Copy link
Contributor

@jeremydesroches do you think we can finish addressing this issue? The few checkboxes left seem pretty straight-forward.

@jeremydesroches
Copy link
Contributor Author

jeremydesroches commented Nov 13, 2020

Yep @jorgeorpinel I'm on it. I'll work through the last unchecked items and verify/update the get started examples.

@jeremydesroches

This comment has been minimized.

@jorgeorpinel

This comment has been minimized.

@jorgeorpinel
Copy link
Contributor

jorgeorpinel commented Nov 22, 2020

Note that the example-get-started repo is no longer used directly in https://dvc.org/doc/start so you could just follow the steps manually @jeremydesroches.

BTW

checkout - ok, get started examples need updating

That command is only used in https://dvc.org/doc/start/data-versioning and seems correct (wouldn't hurt to double check though).

@jorgeorpinel

This comment has been minimized.

@jeremydesroches

This comment has been minimized.

@jorgeorpinel
Copy link
Contributor

@jeremydesroches you can strikethrough or remove the bullets involving "get started" because that will have to be rewritten soon anyway. Is there anything else left here? Thanks

@jeremydesroches
Copy link
Contributor Author

Is there anything else left here?

OK @jorgeorpinel, struck out the "get started" bullets. Nope, nothing left here.

@jorgeorpinel jorgeorpinel added the ✨ epic Placeholder ticket for multi-sprint direction, use story, improvement label Dec 12, 2020
@jorgeorpinel
Copy link
Contributor

Well, thanks for taking care of it!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A: docs Area: user documentation (gatsby-theme-iterative) ✨ epic Placeholder ticket for multi-sprint direction, use story, improvement type: enhancement Something is not clear, small updates, improvement suggestions
Projects
None yet
Development

No branches or pull requests

2 participants