You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The docs are published from the doc-site folder by building with mkdocs and publishing the result to the gh-pages branch, which then acts as the publishing source for Pages. What we want is when a release is published, by pushing tags, the docs site is refreshed with the content. Right now only the head tags is published, but not the release tag. For instance you can see that https://hyperledger-labs.github.io/zeto/head/advanced/locks/ contains the latest docs content, but https://hyperledger-labs.github.io/zeto/latest/ is still at v0.0.11 level.
The text was updated successfully, but these errors were encountered:
The docs are published from the
doc-site
folder by building withmkdocs
and publishing the result to thegh-pages
branch, which then acts as the publishing source for Pages. What we want is when a release is published, by pushing tags, the docs site is refreshed with the content. Right now only thehead
tags is published, but not the release tag. For instance you can see that https://hyperledger-labs.github.io/zeto/head/advanced/locks/ contains the latest docs content, but https://hyperledger-labs.github.io/zeto/latest/ is still atv0.0.11
level.The text was updated successfully, but these errors were encountered: