Revert nbdev CI setup to go back to Jupyter Book #112
Merged
Conversation
This file contains 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
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.
This reverts commit 6d3ca67 that had set up the Continuous Integration for building docs using nbdev. There was an attempt to spin off the documentation to a separate repo (see #102, #103, #104), but we're now going back to the original Jupyter Book setup (#89).
Note that proper branch protections are now in place to prevent direct pushes to the
mainbranch, such that all pushes tomainwill require a Pull Request. The GitHub Pages deployment source has also been changed back to deploying via GitHub Actions rather than from thegh-pagesbranch.