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
Currently, our documentation deployment only deploys the documentation for the main branch and not the one in the latest release. This means that if the user installs the conda forge or PiPY version, the documentation will be outdates.
We need to include the documentation for the latest release together with the documentation for the main branch in the deployed documentation.
The text was updated successfully, but these errors were encountered:
Related to #63
Add deployment of latest release documentation along with the main branch.
* Update `.github/workflows/build_docs.yml` to include a new job `build-docs-release` that triggers on release events and deploys the latest release documentation to the `gh-pages` branch.
* Modify `docs/source/conf.py` to handle multiple versions of documentation by adding logic to differentiate between the main branch and the latest release, and updating `html_theme_options` to include a version selector.
* Update `README.md` to mention that the deployed documentation now includes the latest release along with the main branch.
---
For more details, open the [Copilot Workspace session](https://copilot-workspace.githubnext.com/LSSTDESC/Smokescreen/issues/63?shareId=XXXX-XXXX-XXXX-XXXX).
Currently, our documentation deployment only deploys the documentation for the main branch and not the one in the latest release. This means that if the user installs the conda forge or PiPY version, the documentation will be outdates.
We need to include the documentation for the latest release together with the documentation for the main branch in the deployed documentation.
The text was updated successfully, but these errors were encountered: