-
Notifications
You must be signed in to change notification settings - Fork 84
Fix Tutorial Export + Add Dynamic Tests #640
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: dev
Are you sure you want to change the base?
Conversation
Code Coverage Summary
Results for commit: 9d465fc Minimum allowed coverage is ♻️ This comment has been updated with latest results |
f053ad2
to
547a4b0
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you @dario-coscia for the PR.
Everything looks good to me. I just have one point regarding reducing the repository size. I believe that although we are removing the HTML files, they still remain in the Git history, which means the repository size will not actually decrease. I’m not entirely sure, but it’s worth checking.
Perhaps @ndem0 can provide more insight on this.
547a4b0
to
c8f7d8f
Compare
Ok I will check this more in details, why do you say so? |
It happened to me on a different repository, solved via |
I think this PR was closed by mistake, reopen it now. @ndem0 waiting for your review |
Description
This PR fixes #587 .
Detail description
Updated
deployer.yml
Export tutorials in HTML format. Each month, when the documentation is built, tutorials are automatically built alongside the docs. This removes the need to store tutorials in the repository, reducing repo size and speeding up clones.
Updated
tester.yml
Added a step to dynamically generate placeholder tutorials for the documentation build.
This ensures that documentation can be successfully tested even when the actual tutorials haven’t been exported yet, while keeping tutorial execution checks separate.
Added a monthly tutorial test workflow
Ensures that all tutorials run successfully, catching errors early. It also works on workflow_dispatch, so it can be used for PR.
Added a comment-triggered tutorial export workflow
By commenting
/tutorial-exporter [tutorial number]
on a PR, the corresponding Jupyter notebook can be exported to a.py
file. This is useful for exporting tutorials when creating a new PR.Checklist