Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
This PR adds a GitHub Pages build pipeline that renders every Jupyter notebook into HTML before deployment.
Why it changed
The current GitHub Pages site renders
README.mdfor the homepage, but all notebook links still point to raw.ipynbfiles. On Pages those files are served as notebook JSON, which makes the browser view look broken instead of showing a readable notebook page.User impact
Notebook links on the published site will open rendered HTML pages instead of raw notebook JSON. The homepage keeps the existing README-driven structure, but its links are rewritten for the generated site.
Root cause
GitHub Pages does not automatically render linked
.ipynbfiles from a repository site. The site needed a build step that converts notebooks to static HTML and deploys that output.Validation
I could syntax-check the build script locally, but this desktop environment had local permission and
nbconverttemplate issues that prevented a full local Pages build. The PR includes a clean GitHub Actions workflow so the build runs on a fresh GitHub runner instead.