-
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
start: complete setup for data pipelines #3998
Conversation
p.s. not sure this is wanted per #1943 (comment):
|
Co-authored-by: Restyled.io <[email protected]>
Link Check ReportAll 2 links passed! |
Co-authored-by: Jorge Orpinel <[email protected]>
Co-authored-by: Dave Berenbaum <[email protected]>
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.
180° turn: let's just mention the Data Versioning chapter (and corresponding example repo tag) as preparation then?
p.s. maybe the Pipelines chapter should come before Data and Model Access BTW?
Please also add or commit the source code directory with Git at this point. | ||
|
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.
Note: I'm leaving this sentence out. Also, it's repetitive given "This should be a good time to commit the changes with Git" which is at the end of https://dvc.org/doc/start/data-management/data-pipelines#dependency-graphs-dag (after stage add
).
[Data Versioning](/doc/start/data-management/data-versioning) chapter. | ||
You can get there by cloning the `2-track-data` tag of our | ||
[example-get-started](https://github.com/iterative/example-get-started) | ||
repo. |
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.
I guess this part is also needed? Please commit if so:
repo. | |
repo and using `dvc pull` to get the DVC-tracked data. |
@jorgeorpinel What do you think about closing this PR? It seems like we went into detailed review without resolving the question of whether it's worth doing at all? Edit: Similar discussion applies to #4000 |
Co-authored-by: Restyled.io <[email protected]>
If you don't approve it feel free to close it to avoid further discussion on a non-priority @dberenbaum . Otherwise, if the change can be valuable, please approve+merge (since the work has been done after all). No worries either way! |
Thanks @jorgeorpinel! Despite the narrow scope, I still think there's discussion that would be needed here about what should be added and deleted, so going to close to not distract from priorities. |
Per #1943