Twice per month, run all notebooks in the background. Part 1 of my response to #461. Part 2 will be a template repo that gets built as part of the pysindy docs lives outside of pysindy and has its own CI, as a venue for migration.
These tests will help us fix easy notebook issues in the interim and prioritize moving notebooks off of this repo.
I'm going to merge this now, because the last commit switched the notebook job to on: schedule, which only runs on master, and can only be tested by merging.
I also disabled the draft-pdf workflow for non-master branches. It still applies in PR, however. LMK if that's not desired.
Twice per month, run all notebooks in the background. Part 1 of my response to #461. Part 2 will be a template repo that gets built as part of the pysindy docs lives outside of pysindy and has its own CI, as a venue for migration.
These tests will help us fix easy notebook issues in the interim and prioritize moving notebooks off of this repo.
I'm going to merge this now, because the last commit switched the notebook job to
on: schedule, which only runs on master, and can only be tested by merging.I also disabled the draft-pdf workflow for non-master branches. It still applies in PR, however. LMK if that's not desired.