-
Notifications
You must be signed in to change notification settings - Fork 2
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
feat: Adding new relation for listing private-only entities #611
Conversation
844a52f
to
84a13da
Compare
Pull Request Test Coverage Report for Build 12909527345Details
💛 - Coveralls |
89b92c0
to
07bed78
Compare
07bed78
to
84281e5
Compare
You can access the deployment of this PR at https://renku-ci-ds-611.dev.renku.ch |
Non-blocking: should this be merged into a feature branch instead? As is, the authorization changes are not used anywhere in code. If these changes are part of a larger set of changes, it is easier for everyone contributing to the repository if a feature branch is used. |
Yeah lets merge this into a feature branch. That way if we have to modify the schema before an official release we wont have to do migrations. |
Tearing down the temporary RenkuLab deplyoment for this PR. |
/deploy