-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add testing against release of datalad-next #129
Conversation
and do I need to do anything to make datalad-next patch things up? might relate to the following PR I am yet to get back to: |
not sure why CI didn't run at all. anyways should probably refactor to not have 2x2 with different annex installation methods. |
Testing against a release is sufficient. The get full impact it needs:
|
e386ecc
to
421a097
Compare
=== Do not change lines below === { "chain": [ "064735c5c6a523b311ad8fcaf8ecc7b806458cb9", "fc6c253973517f3da44f67ad04e07105ebaefb57" ], "cmd": "make generate", "dsid": "6b923cfa-a6c6-4bae-941d-e92f6afd5fcb", "exit": 0, "extra_inputs": [], "inputs": [ "scripts/generate", "templates/" ], "outputs": [ "README.md", ".github/workflows/" ], "pwd": "." } ^^^ Do not change lines above ^^^
421a097
to
677cb2b
Compare
nice ! crawler and xnat are chronically red ATM, the others stay green. |
actually I will just keep as is -- let's for now consider it doesn't matter how it fails - with next or without. |
ATM added testing only against release of next and only against datalad-maint. WDYT @mih -- should I change to test against
master
version of datalad-next?TODOs