Open jsheunis opened 3 months ago
@datalad/developers is this all expected behaviour? If so, I think it makes sense to improve documentation (docs and docstrings) to make the use of --publish-depends
and --force=export
after cloning clearer for users. If not, where should we be looking to improve this?
Just leaving a few quick notes from the office hour:
And one more:
Thanks for the investigation and info, @adswa and @mslw. So it seems like everything is expected behaviour technically, but not necessarily intuitive for a new user. I agree that updating the export mode use case docs would be useful.
I am not sure if this is an issue or intended functioning of cloning from a dataset on OSF. It was encountered on Linux during a DataLad workshop by @charlottemock (thanks!)
Environment
Create dataset, add file, save to git
Create osf sibling, check
.git/config
, push to siblingCheck online if the result is as expected
https://osf.io/gfp9r/
Yes it is
Clone from published OSF url into different location of the same system
Here we can see that the publication dependency is missing in the clone. Also, the sibling name is
origin
and notosf
(seedatalad siblings
call). I don't know if either of these (the missing publication dependency and the changed sibling name) are intentional or by design, or a problem? I couldn't find informative docs about this.Add the publication dependency explicitly
This works fine, and was confirmed by inspecting
.git/config
Add changes in the clone, push to origin
This
publish(error)
is the second part of the issue. If I use the--force=export
flag with thepush
, the push of the additional change succeeds.Another note: if I don't configure the publication-dependency in the clone, and then save a change, and push the change to
origin
, the git refs / history is pushed, but not the actual file. This behaviour, or the need to use the--force=export
flag (and why) isn't documented anywhere that I could find.