Skip to content

Commit c303236

Browse files
author
Sylvain MARIE
committed
Fixed documentation: client-side search is now enabled (removed --dirty flag following conversation in https://gitter.im/squidfunk/mkdocs-material)
1 parent c4d0afd commit c303236

File tree

1 file changed

+2
-3
lines changed

1 file changed

+2
-3
lines changed

.travis.yml

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -56,7 +56,7 @@ after_success:
5656
# - pylint mini_lambda # note that at the moment the report is simply lost, we dont transform the result into anything
5757
# ***documentation***
5858
- mkdocs build -f docs/mkdocs.yml
59-
- mv reports/junit site/
59+
- mv reports/junit docs/ # not in site/ anymore so that we do not need to use --dirty (it breaks client-side search)
6060
# mkdocs gh-deploy requires special care :
6161
# ---grant the possibility to push on the repo---
6262
- openssl aes-256-cbc -K $encrypted_fdc2c20d7f8b_key -iv $encrypted_fdc2c20d7f8b_iv -in ci_tools/github_travis_rsa.enc -out ci_tools/github_travis_rsa -d
@@ -71,8 +71,7 @@ after_success:
7171
git remote add gh-remote "${GH_REF}";
7272
git fetch gh-remote && git fetch gh-remote gh-pages:gh-pages; # make sure we have the latest gh-remote
7373
# push but only if this is not a build triggered by a pull request
74-
# note: here we use the --dirty flag so that mkdocs does not clean the additional reports that we copied in the site
75-
if [ "${TRAVIS_PULL_REQUEST}" = "false" ] && [ "${TRAVIS_PYTHON_VERSION}" = "3.5" ]; then echo "Pushing to github"; PYTHONPATH=mini_lambda/ mkdocs gh-deploy -v --dirty -f docs/mkdocs.yml --remote-name gh-remote; git push gh-remote gh-pages; fi;
74+
if [ "${TRAVIS_PULL_REQUEST}" = "false" ] && [ "${TRAVIS_PYTHON_VERSION}" = "3.5" ]; then echo "Pushing to github"; PYTHONPATH=mini_lambda/ mkdocs gh-deploy -v -f docs/mkdocs.yml --remote-name gh-remote; git push gh-remote gh-pages; fi;
7675
else
7776
echo "File 'ci_tools/github_travis_rsa' has not been created, please check your encrypted repo token in .travis.yml, on the line starting with 'openssl aes-256-cbc...'"
7877
fi

0 commit comments

Comments
 (0)