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
Hi. Thanks for your great work on sphinx-multiversion.
I have a API documentation generated using sphinx-apidoc and sphinx-build.
I would like to generate a versioned api documentation using sphinx-multiversion in a CI environment with Jenkins.
If possible, I would like to avoid committing/pushing the output of sphinx-apidoc onto the respective branch.
My question is the following: is it possible to tell sphinx-multiversion to run sphinx-apidoc after sphinx-multiversion has checked-out the respective branch, so that sphinx-multiversion can use the rst files generated by sphinx-apidoc.
Thanks in advance for your help.
The text was updated successfully, but these errors were encountered:
You can use this to get this working: https://pypi.org/project/sphinxcontrib-apidoc/ - it automatically runs the configured apidoc stuff on any sphinx build, including each version build.
Hi. Thanks for your great work on sphinx-multiversion.
I have a API documentation generated using
sphinx-apidoc
andsphinx-build
.I would like to generate a versioned api documentation using sphinx-multiversion in a CI environment with Jenkins.
If possible, I would like to avoid committing/pushing the output of
sphinx-apidoc
onto the respective branch.My question is the following: is it possible to tell
sphinx-multiversion
to runsphinx-apidoc
aftersphinx-multiversion
has checked-out the respective branch, so thatsphinx-multiversion
can use the rst files generated bysphinx-apidoc
.Thanks in advance for your help.
The text was updated successfully, but these errors were encountered: