Paweł Redzyński

Include test for #8159

What will be the `error` data used for? Do we only want to pass the error message to the user? Or will there be some logic involved with processing the...

No, but I believe we could include it as a part of implementing iterative/vscode-dvc#1757

I consider it as a part of aforementioned issue on `vscode` - but the estimation for vscode depends on research on studio side. It is not yet finished.

Note to self: since returning errors will probably require data structure change, we need to remember to get rid of filling `rev` in datapoints - as vscode sometimes need to...

@shortcipher3 regarding the plots it should be already available in latest release: ```yaml #dvc.yaml stages: #

After some quick research I have following conclusions: 1. `git pull` - we can use `post-merge` hook to do `dvc pull` 2. `git push` - I would like to discuss...

@efiop > But not every pull involves merge. It might do rebase instead. Well we can use `post-rewrite`, according to the [documentation](https://git-scm.com/docs/githooks#_post_rewrite) it is triggered after `amend` or `rebase`, but...

>But that one is going to be called not only on git pull but also on regular amend and rebase. Not sure if it is something we actually want. What...

@pokey is right, its still an issue: ``` def test_checkout_empty_dir(tmp_dir, dvc): tmp_dir.dvc_gen({"empty_dir":{}}) tmp_dir.gen({"empty_dir": {"subdir": {}}}) dvc.checkout() assert not os.path.exists(tmp_dir / "empty_dir" / "subdir") ``` This test fails. Seems like our...