-
Notifications
You must be signed in to change notification settings - Fork 32
CI: Add workflow for documentation generation #40
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
Conversation
fb808dd
to
0aa7b96
Compare
8f7655f
to
fd3147d
Compare
I tried to add a workflow to update the status to give a link to the generated documentation, but that doesn't seem to have permission to run. We can figure out if there is a way to do that. For now, you can view the generated docs here. |
.github/workflows/docs.yml
Outdated
|
||
jobs: | ||
generate-docs: | ||
runs-on: ubuntu-latest |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would consider pinning this to a specific version to avoid surprises.
Add a target to the build `rustdoc` that will generate the rust documentation. The documentation will be placed in a target-specific directory under `build/rust/target/...`. There is some duplication in the cmake file, as I can't figure out how to factor this out into a variable and maintain the proper quoting of the space separated strings. Signed-off-by: David Brown <[email protected]>
The rust docs don't have a convenient index file, so add this one, which will be included in the docs. Signed-off-by: David Brown <[email protected]>
This attempts to build the project documentation, for PRs uploading it to a working directory for the PR. Signed-off-by: David Brown <[email protected]>
Don't rely on "latest" but run on a specific version. Pick the 24.04, which has recently become available. Signed-off-by: David Brown <[email protected]>
This attempts to build the project documentation, for PRs uploading it to a working directory for the PR.
This PR will likely need lots of revisions, as it is primarily tested by uploading the PR.
I haven't figured out how to get a workflow that has permissions to add a comment or status giving a link to the docs, so we can do that later. For now, the docs for this change can be visited manually.