Closed mauriciovieira closed 7 years ago
Sounds like a good idea. We are currently using mkDocs to build the docs, could that also be automated?
But someone with administrative privileges on the repository must setup the keys in order to allow travis to push to gh-pages branch.
I can help with the key setup. Lets discuss this further in chat.
I did the commits on master. It's just a matter of turning it on at https://travis-ci.org/profile/apinf and setting up the keys.
@brylie Can you take a look at this setup? Or I can do it, if you give me admin clearance for this repo.
You now have admin access.
@brylie. Thank you. It's done https://travis-ci.org/apinf/docs/builds/262299235
@brylie is there a historical reason for not having this repository deployed by travis (or other continuous integration software) after each commit to master?
Recently I got a gh-pages repository configured to deploy any commit to master (after some trial and errors), and would like to suggest the same kind of build for this repository.