Open jaheba opened 2 years ago
/cc @rsnirwan @lostella
We could have some environment variable control whether to run the notebooks in "development" or "release" mode, and use that to control stuff like number of epochs, number of trials, or anything. But doing it in such a way that doesn't "pollute" the output notebook is challenging: maybe some pre-processing of the markdown files? Something like
[...]
epochs = $1; 10$
[...]
that gets substituted with epochs = 1
in development mode, and epochs = 10
in release mode.
Just an idea.
Was thinking something similar. We could have some template running.
But maybe we are just more radical and only run the notebooks on push and not for pull_request.
But maybe we are just more radical and only run the notebooks on push and not for pull_request.
Sounds good to me, but then we better make sure we check the output status of the docs build every now and then. How about putting a badge in the README for it?
We would still run the full docs workflow on push
, but not for the individual pull_requests, except when https://github.com/awslabs/gluon-ts/labels/pr%3Adocs-build-notebook is used.
We can still add another layer using Jinja2 to compile the tutorials as templates.
Running the tutorial notebooks is slow:
Ideally we reduce the runtime as much as possible for the workflows to run.
However, I can see that we would like to run them for longer when publishing the release docs.