tools: build docs on netlify rather than travis #759
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
Building as an after-success hook on travis hid failures. Building on netlify directly will let the docs be a parallel effort and should catch failures at PR time correctly. This is a squash of a few things: - travis: don't spew zip info - netlify: try building docs on there instead of travis - tools: can't use sudo on netlify - tools: ignore built doc artifacts - travis: remove netlify from travis
ppannuto
added
documentation
P-Upkeep
brghena
approved these changes
Feb 28, 2018
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.
Pull Request Overview
Building as an after-success hook on travis hid failures. Building on netlify
directly will let the docs be a parallel effort and should catch failures at
PR time correctly.
This is a squash of a few things: