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
Instead of the RTD application always triggering its jobs, first check if in the commit there exists a github workflow that triggers readthedocs/actions/build (or whatever the name will end up being), and if it exists, do NOT trigger the default rtd workflow. Instead, have the action create an appropriate request to trigger it.
This is similar to dfm/rtds-action, but in that case it does not trigger the rtd workflow, it simply uploads the generated documentation. This action is intended to be much simpler, just to trigger the already present rtd workflow.
Benefit
fine-grained control of when a RTD action is performed, e.g. only if docs folder is altered
The text was updated successfully, but these errors were encountered:
We are integrating R documents and JVM documents into the Sphinx site. These documents are built separately due to resource requirements and the rtd builder needs to wait and download the artifacts. Having a GitHub action to trigger RTD build can solve the problem.
Suggestion
Instead of the RTD application always triggering its jobs, first check if in the commit there exists a github workflow that triggers
readthedocs/actions/build
(or whatever the name will end up being), and if it exists, do NOT trigger the default rtd workflow. Instead, have the action create an appropriate request to trigger it.This is similar to dfm/rtds-action, but in that case it does not trigger the rtd workflow, it simply uploads the generated documentation. This action is intended to be much simpler, just to trigger the already present rtd workflow.
Benefit
docs
folder is alteredThe text was updated successfully, but these errors were encountered: