add `dvc push` to the instructions after `dvc repro`

[Casyfill]

(See description in #2359 (comment) below.)

[shcheklein]

Some context:

Users tend to forget to call dvc push when dvc repro is done, to save the file to the cloud. Probably it affects the most automation scenarios, when you call dvc repro from a script.

@Casyfill :

1. Is my assumption about the scenario, correct?
2. Do you call git commit, git push in your case? Just trying to understand can it be solved by git hooks after all?

[shcheklein]

Solving this #2362 might solve the problem. I would add the message anyway. It does not hurt.

[Casyfill]

yes, absolutely. and indeed, does not hurt :-)

[efiop]

@shcheklein solving #2362 won't make pre-commit hook run dvc push :) We've talked about it in the original chat and it seems like dvc push on commit is not a generic enough scenario to be included in our default hooks.

[shcheklein]

I meant that running dvc push on git push might be enough in the particular case this topic originates. I totally understand that it's not a replacement for running dvc push after each repro.

[efiop]

Ah, got it @shcheklein .

Btw, this is just a random thought, but this topic makes me think about dvc hooks that dvc would call after some operations 🙂 E.g. you could write .dvc/hooks/post-repro to run dvc push. I wonder if this mechanism is viable in general and if it would be useful in any other scenarios.

[shcheklein]

It's probably viable. But let's implement it in a proper way if we decide to :) Not the way git does (one single executable 🤦‍♂.)

[efiop]

Yep, maybe a yaml config like pre-commit has would be a better choice 🙂 Nice thing about these hooks is that they would be actually stored by git, so you won't have to setup your hooks after each clone. Created #2363 for that. @Casyfill if you have any thoughts about it, please feel free to share them 🙂

I'd like to work on this