Enable downloadable documentation with readthedocs #213
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 is so that we can auto-generate pdf and epub documentation from readthedocs. It looks like this: https://pypromice.readthedocs.io/_/downloads/en/v1.2.1/pdf/
We previously did this automatically, but it changed when readthedocs versioning had to be updated ( in #191). So we now have to specify pdf/epub builds in the readthedocs configuration file in the repo.
I thought this might be useful in general, and also make it quicker for us to pull the readthedocs information into the GC-Net report.