Repository navigation
Upload doc artifacts from doc build run - #1092
Merged
Merged
Conversation
Build artifacts, constructed in the build docs workflow, are zipped together and can be downloaded and inspected. * .github/workflows/docs.yml (jobs): Use actions/upload-artifact.
matsl
force-pushed
the
pr_upload_build_artifacts
branch
from
October 30, 2026 16:02
bb0c685 to
26909e4
Compare
matsl
marked this pull request as ready for review
October 30, 2026 18:11
rswgnu
requested changes
Oct 30, 2026
rswgnu
left a comment
Owner
There was a problem hiding this comment.
The date seems to be the only change on the hyperbole.texi file, so just kill that change and resubmit.
Collaborator
Author
|
Yes, there had to be one change in a doc to trigger the doc build to |
rswgnu
approved these changes
Oct 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Upload doc artifacts from doc build run into a zip-file that can be viewed locally.
Why
Since we build the docs in the build-docs workflow it is interesting to see how they look without having to make them part of the PR. Especially in cases where we change the way the docs are generated.
Current PR #1091 is one example that would benefit from this update.