workflow for publishing docs #482
Conversation
| @@ -0,0 +1 @@ | |||
| Sphinx | |||
There was a problem hiding this comment.
Is it possible to move this requirement document to doc? So that it will be clear that it's requirements only for Documentation, not for the full oneMKL build.
|
Would it be sufficient to use "publishing from a branch"? We might also want to restrict publishing only when there are changes in the |
|
It's a different implementation to publish from a branch. Publishing from a branch is a little more manual, but also more flexible. I can make the changes, but I would rather do it after #483 is merged. It will work better if there is a single workflow file so I can structure checks, unit tests, and doc publishing as CI jobs that depend on each other. With that in mind, I am closing this PR. It will help me to wrap this up if we can get #483 merged and I can add new CI jobs there. |
Description
Build/publish documentation automatically when merging to develop. To enable this workflow, someone with admin rights needs to click settings/pages. And then change the "source" to "GitHub Actions"
Partially addresses #459. I also wasted time following the conan instructions, then found that conan support was dropped. I also saw that someone had updated the documentation to reflect the change. But I never saw that because the new documentation was not published. The published documentation has not been updated for 2 years!