Tell us about your environment
Currently, MarkBind documentations are deployed manually during a release.
We now have a way to automate markbind deploy with Travis.
We can write a script such that, when Travis realize that the commit has a version tag on it (by checking $TRAVIS_TAG == 'vx.x.x'), then Travis will build and use markbind deploy -t/--travis to push the new version's documentation automatically to our repo's gh-pages.
Tell us about your environment
Currently, MarkBind documentations are deployed manually during a release.
We now have a way to automate
markbind deploywith Travis.We can write a script such that, when Travis realize that the commit has a version tag on it (by checking
$TRAVIS_TAG == 'vx.x.x'), then Travis will build and usemarkbind deploy -t/--travisto push the new version's documentation automatically to our repo'sgh-pages.