-
Notifications
You must be signed in to change notification settings - Fork 24
Publish SHACL to repo #814
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
Conversation
…/renku-python into 755-kg-validation
…/renku-python into 755-kg-validation
|
I see. But that ability should probably be part of the schema versioning itself since we gonna most likely need it inside the core module for migrations. Also, having a new directory for every changed schema version (vs. for every commit) makes it easier/possible to track changes of schema through time (I think the same wouldn't be the case after 200 commits on master with current setup). I guess there is a tradeoff for both. |
|
i changed it so it only gets executed when |
jsam
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for setting this up. It's pretty cool!
* Adds SHACL validation to renku doctor * Adds renku log tests * Adds --strict option to renku log for shape validation
Description
Github action to copy the
shacl_shape.jsonto a different repository on commit to master with version.Currently configured to go to https://github.com/Panaetius/SHACL_test_repo for testing.
Access Token needs to be generated for this with rights to the final repository where the SHACL should end up in. Until then it's WIP and it pushes to the test repo on every commit (not just on commit to master)
Closes SwissDataScienceCenter/renku#685