Closed jag3773 closed 4 years ago
Consider whether this should include setting up some sort of "mega schema" that is one file including all the relevant pieces of the schema.
I setup an example action which tests against the develop
branch of SB.
I ran it against develop
because I'm assuming we will want to do releases of the schema in conjunction with updated example repositories. Hence, tying these examples repos to develop
seems like the best way to keep them in sync.
Note that I also converted the validation running in this repository to run via Github Actions too (#202 ).
Steps to setup this github action on your example repo would look something like this...
[![CI](https://github.com/bible-technology/sb_textStories/workflows/CI/badge.svg?branch=master)](https://github.com/bible-technology/sb_textStories/actions)
Finally, merge your PR and verify that you've got CI badge that shows passing.
For all of the issues in https://github.com/bible-technology/scripture-burrito/milestone/6 it would be a lot easier to setup automated validation if we had a Github Action that we could apply to the repositories.
Alternately, we could copy our Travis CI configuration but since Github Actions are an integrated service it seems preferable to go that route.