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
The API and code documentation written in Sphinx is not built automatically. This is an undesirable situation, as there is a risk that documentation for new features is not available, and even worse, that there will be outdated information present.
Ideally, I want to build the documentation that is on http://docs.opencultuurdata.nl/ with every commit on master (i.e. when we do a release), preferably with the inclusion of a version number.
In addition to that, it would be useful to build the documentation in a separate folder on every commit on a branch, in order to make the life the one testing easier.
My guess is that webhooks could be a suitable solution for that.
The text was updated successfully, but these errors were encountered:
The API and code documentation written in Sphinx is not built automatically. This is an undesirable situation, as there is a risk that documentation for new features is not available, and even worse, that there will be outdated information present.
Ideally, I want to build the documentation that is on http://docs.opencultuurdata.nl/ with every commit on
master
(i.e. when we do a release), preferably with the inclusion of a version number.In addition to that, it would be useful to build the documentation in a separate folder on every commit on a branch, in order to make the life the one testing easier.
My guess is that webhooks could be a suitable solution for that.
The text was updated successfully, but these errors were encountered: