Skip to content
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

Merged
merged 5 commits into from
Sep 17, 2024
Merged

Add testing against release of datalad-next #129

merged 5 commits into from
Sep 17, 2024

Conversation

yarikoptic
Copy link
Member

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

  • add to the README.md table

@yarikoptic
Copy link
Member Author

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:

@yarikoptic
Copy link
Member Author

not sure why CI didn't run at all. anyways should probably refactor to not have 2x2 with different annex installation methods.

@mih
Copy link
Member

mih commented Sep 16, 2024

Testing against a release is sufficient.

The get full impact it needs:

git config --global --add datalad.extensions.load next

=== 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 ^^^
@yarikoptic
Copy link
Member Author

nice ! crawler and xnat are chronically red ATM, the others stay green.
but I think I forgot that for the badge we need pretty much a separate workflow , not just a matrix run, so I will have to redo at that level :-/ later...

@yarikoptic
Copy link
Member Author

actually I will just keep as is -- let's for now consider it doesn't matter how it fails - with next or without.

@yarikoptic yarikoptic merged commit f06a306 into master Sep 17, 2024
50 of 60 checks passed
@yarikoptic yarikoptic deleted the enh-next branch October 14, 2024 12:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants