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
Triggering a new build for the master branch with the REST API should update the online document for "latest" after the build is finished.
Actual Result
The new document is not displayed. Also, the resulting page from the new build is missing.
Context
We use the REST API to trigger a new build after our CI for building document artifacts is completed. The conf.py file fetches these artifacts to render the document during the sphinx build. As a result, the read the doc build service is run twice, the first time invoked by the default GitHub webhook and the second time by a custom GitHub action that invokes the REST API. The build from the second run must be used as the final result.
We hope there's a better way to add dependencies between GitHub action and read the doc build. But for now, it would be great to update the latest doc with the REST API.
The text was updated successfully, but these errors were encountered:
Details
Expected Result
Triggering a new build for the master branch with the REST API should update the online document for "latest" after the build is finished.
Actual Result
The new document is not displayed. Also, the resulting page from the new build is missing.
Context
We use the REST API to trigger a new build after our CI for building document artifacts is completed. The
conf.py
file fetches these artifacts to render the document during the sphinx build. As a result, the read the doc build service is run twice, the first time invoked by the default GitHub webhook and the second time by a custom GitHub action that invokes the REST API. The build from the second run must be used as the final result.We hope there's a better way to add dependencies between GitHub action and read the doc build. But for now, it would be great to update the latest doc with the REST API.
The text was updated successfully, but these errors were encountered: