Skip to content
This repository has been archived by the owner on Jun 28, 2021. It is now read-only.

push Push staged changes in the local registry to the remote one #8

Open
kzscisoft opened this issue May 14, 2021 · 2 comments
Open
Labels

Comments

@kzscisoft
Copy link
Collaborator

Performs the actual sync, unlike git you do not need to add any files if they already being tracked. However you should add runs in order to push them (means if you do a run and it is a mistake you won't accidentally push it to the remote).

@kzscisoft kzscisoft added the cli label May 14, 2021
@richardreeve
Copy link
Member

If a run is a mistake, are its output files automatically being "tracked"? I guess I don't know what is automatically tracked... I would have thought that nothing is, but if you add a file, then you also add the run and all of the newly registered inputs, and if you add a run, then you all add all of the files (input and output). I may be misunderstanding what you're saying though...

@kzscisoft
Copy link
Collaborator Author

kzscisoft commented May 17, 2021

My understanding is that a run is like a "packet" of information (which ultimately is a JSON post to the remote registry) defined by the user (through whichever implementation they are using) which is the properties of the run and also description of any files associated with it. By treating it as a single entity/packet then add would include everything. Unless you can think of a situation where you would only want to push some of the metadata not all of it?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants