Set up automated testing for 9.3/10.1 branches

[curiousdannii]

It would be great to set up automated testing for the 9.3/10.1 branches, so that any files that are updated by a pull request get tested against those I7 releases. Probably all we can do is to test if they compile after being included, but maybe we could also check if their examples compile too?

[zedlopez]

My dream for a long while has been that my smoketester results (which now includes compiling the examples) would be automatically generated and committed to the extensions repo's github pages.

But it's also the case that inf7 had become a godawful mess before I engaged in all my recent hack-and-slashery to support v10 and it'd be an understatement to say it's not production-ready. And while it's maybe reasonable to hope I could write its successor before the end of 2022, it won't be soon. (If anyone else feels like tackling it, they should!)

[curiousdannii]

It probably doesn't need to be that complex, especially once the Linux CLI packages are published.

On the other hand, maybe people would appreciate having it be available as a Github Action one day.

My dream for a long while has been that my smoketester results (which now includes compiling the examples) would be automatically generated and committed to the extensions repo's github pages.

It would be best I think for it to run as a Github action, listening for any commits to the master/9.3/10.1 branches, and then would put its output directly into a gh-pages branch.

[neroden]

Just in case it wasn't totally clear: I would strongly like to see the Smoketest automatically running on the master branch where the work-in-progress is. It would be very useful. Basically, only after my extension is passing the smoketest, would I try to put it into the v10 branch.