Revert how we deploy docs (#9394)

DO NOT DELETE THIS TEXT

#### Please note

> Please read this information carefully. You can run `./scripts/pre-commit.php` to check your code before submitting.

- [ ] Have you followed our [code guidelines?](http://docs.librenms.org/Developing/Code-Guidelines/)

#### Testers

If you would like to test this pull request then please run: `./scripts/github-apply <pr_id>`, i.e `./scripts/github-apply 5926`
After you are done testing, you can remove the changes with `./scripts/github-remove`.  If there are schema changes, you can ask on discord how to revert.
This commit is contained in:
Neil Lathwood
2018-10-27 23:16:41 +01:00
committed by GitHub
parent 1ee2e8e0e0
commit 0726d479ce

View File

@@ -27,11 +27,10 @@ build_result=$?
# Only deploy after merging to master
if [ "$build_result" == "0" -a "$TRAVIS_PULL_REQUEST" == "false" -a "$TRAVIS_BRANCH" == "master" ]; then
cd out/
mkdocs gh-deploy --config-file ../mkdocs.yml --remote-branch master
# touch .
# git add -A .
# git commit -m "GH-Pages update by travis after $TRAVIS_COMMIT"
# git push -q origin master
touch .
git add -A .
git commit -m "GH-Pages update by travis after $TRAVIS_COMMIT"
git push -q origin master
else
exit ${build_result} # return doc build result
fi