-
Notifications
You must be signed in to change notification settings - Fork 38
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
3.0 updates #684
3.0 updates #684
Conversation
Let's wait a few days on this since there is no rush and want to make sure we don't forget something. Then we can merge at the start of next week if nothing comes up. |
We also need accompanying docs updates. |
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.
Nothing wrong with the PR AFAICT, but let's hold on this for #687
Codecov ReportPatch coverage is 📢 Thoughts on this report? Let us know!. |
* add dvcyaml to root * clean up dvcyaml implementation * fix existing tests * add new tests * add unit tests for updating dvcyaml * use posix paths * don't resolve symlinks * drop entire dvclive dir on cleanup * fix studio tests * revert cleanup changes * unify rel_path util func * cleanup test * refactor tests * add test for multiple dvclive instances * put dvc_file logic into _init_dvc_file --------- Co-authored-by: daavoo <[email protected]>
Fallback to `None` when conditions are not met for other types.
Rename test_frameworks to frameworks.
@dberenbaum should we just merge this into main? I don't think there is reason to wait and unlikely needing to release 2.X |
I was thinking of waiting on iterative/dvc#9898 since if we have to release before then, it will be ugly for existing projects |
Need to update dvc version before merging |
* drop dvc.yaml prefix from studio plots * refactor * drop .dvc files * dvc version bump
for more information, see https://pre-commit.ci
Closes #499
Closes #484
Closes #459