Closed mih closed 6 years ago
looking into it. I think I will just make crawler to default to start new branches (incoming, incoming-processed) from master
branch. It might have undesired side-effects (e.g. if someone starts somewhere late in the "master" branch, and then those branches would inherit everything it has, instead of starting clean), but I do not see a better way around since we do need to set .gitattributes for the md5 backend while working in those branches, and that is where the conflict emerges -- incoming
having it with the backend set and master having not only that (which was ok since identical), but also with setting for what to commit to git/annex
Sounds sane to me. I don't see this "late crawler use" is being a comon pattern.
@yarikoptic As discovered by https://github.com/datalad/datalad/pull/2487, the PR https://github.com/datalad/datalad/pull/1597 broke the OpenFMRI pipeline.
Full log: https://travis-ci.org/datalad/datalad/jobs/378021286
And actually more than Openfmri is broken now:
https://travis-ci.org/datalad/datalad-crawler/jobs/378037035
It seems the pipelines (or just the tests) cannot deal with the situation that a dataset already comes with a
.gitattributes
file.Also FYI @bpoldrack