If a computation is started via the datalad-remake git annex special remote, it should recreate file content bit-identical. For annexed files, this is verified by git annex via a comparison of the file keys. But a datalad make execution might also modify non-annex files, e.g. text files. This must not happen, if the special remote triggers the computation.
To prevent the change of non-annex files when the special remote triggers a computation, the collect phase should either:
- compare the existing text file and the generated text, or
- refuse to copy non-annex files from the workspace into the dataset
If a computation is started via the datalad-remake git annex special remote, it should recreate file content bit-identical. For annexed files, this is verified by git annex via a comparison of the file keys. But a datalad make execution might also modify non-annex files, e.g. text files. This must not happen, if the special remote triggers the computation.
To prevent the change of non-annex files when the special remote triggers a computation, the collect phase should either: