Skip to content

Add experimental RTD doc support #105

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 4, 2025
Merged

Conversation

Ozaq
Copy link
Contributor

@Ozaq Ozaq commented Apr 4, 2025

This commit adds RTD doc builds with PR-Preview support. This is still an experiment to see how we want to continue on this.

Notes:

  • The build in .readthedocs.yaml is horrific and has to be done because I inist on running the same doc generation locally as in the ci.
  • .readthedocs.yaml is very limited in what it allows. Dependencies need to be installable via pip. No system packages can be installed
  • My initial attempt to build doc in one of our GH Actions and simply unpack the tarball would work in principle but is complicated to setup so that it offers feature parity to the default RTD/GH integration. When using a prebuild doc tarball you need to wait for the tarball to be created. This means you can no longer use the installed webhook as this will get triggeren on push. You then need to use the RTD rest API to trigger the build once the doc build is finished. This then in turn means you need to call the GH rest api from the RTD build to signal start / success / failure of the build back to GH.

@Ozaq Ozaq added the documentation Improvements or additions to documentation label Apr 4, 2025
This commit adds RTD doc builds with PR-Preview support. This is still
an experiment to see how we want to continue on this.

Notes:
- The build in .readthedocs.yaml is horrific and has to be done because
  I inist on running the same doc generation locally as in the ci.
- .readthedocs.yaml is very limited in what it allows. Dependencies need
  to be installable via pip. No system packages can be installed
- My initial attempt to build doc in one of our GH Actions and simply
  unpack the tarball would work in principle but is complicated to setup
  so that it offers feature parity to the default RTD/GH integration.
  When using a prebuild doc tarball you need to wait for the tarball to
  be created. This means you can no longer use the installed webhook as
  this will get triggeren on push. You then need to use the RTD rest API
  to trigger the build once the doc build is finished. This then in turn
  means you need to call the GH rest api from the RTD build to signal
  start / success / failure of the build back to GH.
@Ozaq Ozaq force-pushed the feature/add-doc-preview branch from a3af3ba to 1eddc71 Compare April 4, 2025 20:10
@codecov-commenter
Copy link

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 63.84%. Comparing base (51425aa) to head (1eddc71).

Additional details and impacted files
@@           Coverage Diff            @@
##           develop     #105   +/-   ##
========================================
  Coverage    63.84%   63.84%           
========================================
  Files          281      281           
  Lines        15815    15815           
  Branches      1643     1643           
========================================
  Hits         10097    10097           
  Misses        5718     5718           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@simondsmart simondsmart merged commit d9c77cd into develop Apr 4, 2025
147 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants