Currently notebooks are executed locally before being committed. It would be useful to add CI workflows that run them in a clean environment and ensure they execute without errors (and potentially warnings?)
Two workflows could be considered: one against the latest development versions of the Echostack packages (e.g., triggered on pushes to main in any (?) Echostack repositories), and one against the latest released versions to ensure the published examples remain functional. The required notebook dependencies should also be defined in pyproject.toml.
Rendering notebooks directly in RTD could also be considered, though some heavier notebooks may exceed memory limits.
Currently notebooks are executed locally before being committed. It would be useful to add CI workflows that run them in a clean environment and ensure they execute without errors (and potentially warnings?)
Two workflows could be considered: one against the latest development versions of the Echostack packages (e.g., triggered on pushes to
mainin any (?) Echostack repositories), and one against the latest released versions to ensure the published examples remain functional. The required notebook dependencies should also be defined inpyproject.toml.Rendering notebooks directly in RTD could also be considered, though some heavier notebooks may exceed memory limits.