-
Notifications
You must be signed in to change notification settings - Fork 5
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 json examples for material and asset files #29
Add json examples for material and asset files #29
Conversation
… files Signed-off-by: ClemensLinnhoff <[email protected]>
Signed-off-by: ClemensLinnhoff <[email protected]>
Signed-off-by: ClemensLinnhoff <[email protected]>
@nakohdo What is the state of the JSON validation pipeline? |
Signed-off-by: Frank Ralf <[email protected]>
Signed-off-by: Frank Ralf <[email protected]>
Hi @ClemensLinnhoff, |
Good idea. It needs to be triggered on changes in the example folder or the schema folder. |
Signed-off-by: ClemensLinnhoff <[email protected]>
Signed-off-by: ClemensLinnhoff <[email protected]>
Signed-off-by: Frank Ralf <[email protected]>
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.
No remarks from my side.
Signed-off-by: Diego Sánchez [email protected]
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.
CCB decision 02.08.24: Merge as is |
Describe your changes
Issue ticket number and link
#28
Mention a member
@nakohdo You could take this branch and continue with the JSON validation pipeline.
Checklist before requesting a review