Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tavis CI - automate build process and gh-pages deploy from master branch #2

Open
maxiride opened this issue Sep 16, 2017 · 0 comments

Comments

@maxiride
Copy link
Collaborator

maxiride commented Sep 16, 2017

The state of the art of using mkdocs to update the documentation would be to:

  • PR in the master branch any change\etc from develop
  • Pull locally the master
  • Build the docs with mkdocs build
  • Push to the gh-pages branch the builded documentations using the built-in mkdocs gh-deploy

Instead of having to manually do all this stuff and use mkdocs gh-deploy from the local master branch to update the docs, I stumbled upon this article that explains how travis-ci can also build and deploy from the source. This way we can just worry about commits and PR to master and travis will do the rest.

Is it worth the implementation? For me, yes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant