Using doc instead of pandas-doc for the build #2
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
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.
@jorisvandenbossche, @stijnvanhoey, if that's ok I'll make travis build the directory
docinstead ofpandas-doc. I'm making a script that performs the operations to change the theme, so besides working in this repo, then it can be applied to the pandas repo. This way we don't have complex merges if the documentation changes in the main repo, and here we have an old copy. And for that script to be simpler, I prefer to replicate the same structure as the pandas repo here (that's why the changepandas-docbydoc).This change means that if you want to update your branches and have the build working, you should rename the directory there.