Suggesting to introduce a Github action that runs the webpage build to catch problems like #205. This action runs on pull requests and pushes to master, and simply checks whether the webpage can be built.
Moving forward, we can add more actions, e.g. automating the navigation generation (see #44, which I had totally forgotten about). But for now, this is an easy way to make sure that PRs don't break things.
I don't have the rights to merge this myself but I think it's good to go, so please feel free to merge it if you think it's ready @davidlmobley or @mrshirts.
Suggesting to introduce a Github action that runs the webpage build to catch problems like #205. This action runs on pull requests and pushes to master, and simply checks whether the webpage can be built.
See https://github.com/ptmerz/livecomsjournal.github.io/pull/1 for an example: In that PR, I undid the fix in #206. The action catches this and blocks merging.
Moving forward, we can add more actions, e.g. automating the navigation generation (see #44, which I had totally forgotten about). But for now, this is an easy way to make sure that PRs don't break things.