-
Notifications
You must be signed in to change notification settings - Fork 171
Stop tracking cached files and Jupyter notebook hashes in doc builds #425
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
Conversation
/ok to test |
This comment has been minimized.
This comment has been minimized.
/ok to test |
2 similar comments
/ok to test |
/ok to test |
3bd7db0
to
532752e
Compare
/ok to test |
Labeling as blocked on #424. It builds off of a commit to notebook execution. |
/ok to test |
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.
Q: with #424, do we still need this change?
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.
We do because Jupyter notebook still generates new hashes for the jupytext
and kernelspec
for every commit
|
close #351
.doctrees
contain cached build files and don't impact html rendering. Store them outside of html build path.overview.md
has page settings that triggers Jupyter notebook execution. Since the settings have minimal impact on displayed page, remove them to avoid hash regeneration.