Get docs working via Travis & github pages #8
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
|
A GITHUB_TOKEN will need to be added to Travis CI env vars before the push from master can work. |
|
Per discussion in #9, it might make sense to drop all the references to API for now. |
alexandrevicenzi
approved these changes
Mar 21, 2019
docs/conf.py
Outdated
| # -- Project information ----------------------------------------------------- | ||
|
|
||
| project = 'ubi-population-tool' | ||
| copyright = '2018, Red Hat' |
Basic skeleton of docs are in place. Currently, the classes/methods appearing in "API reference" should be considered as examples only. I'm not sure exactly what should go in there as it still seems a bit unclear what is and isn't public API. The main goal here is to get the doc building toolchain up and running.
alexandrevicenzi
approved these changes
Mar 21, 2019
|
Token added to travis, merging. |
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.
Basic skeleton of docs are in place.
Currently, the classes/methods appearing in "API reference" should
be considered as examples only. I'm not sure exactly what should
go in there as it still seems a bit unclear what is and isn't
public API. The main goal here is to get the doc building toolchain
up and running.