Because paratest doesn't test the chapel-blog repository, it's easy for developers to merge PRs that break the blog and then have to fix them the next day. This issue asks whether we could:
- add a CI to this repository to test the blog prior to merge
- extend
paratest to grab and test chapel-blog by default
to avoid such surprises.
Because
paratestdoesn't test the chapel-blog repository, it's easy for developers to merge PRs that break the blog and then have to fix them the next day. This issue asks whether we could:paratestto grab and testchapel-blogby defaultto avoid such surprises.