Use doctr to deploy built docs to GH pages. #267
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
danielballan
force-pushed
the
use-doctr
branch
4 times, most recently
from
49049b4 to
f29930a
Compare
danielballan
force-pushed
the
use-doctr
branch
from
f29930a to
5b31a99
Compare
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.
I have been doing this sporadically by hand, and I'd like to put an automated solution up so that the documentation stays current.
A downside of this approach is that we will be running Circle-CI (for tests) and Travis-CI (just to publish docs) because there is a no equivalent integration for Circle-CI. In a Slack conversation, @Mr0grog and I agreed that once the project and the documentation are more built out and #206 is behind us, we will revisit this and either deploy the docs from Circle-CI using yet-to-be-written deployment code or move to readthedocs.org.