CI: Upload documentation HTML ZIP archive and PDF file as release assets #3814
Conversation
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
seisman
added
maintenance
michaelgrund
approved these changes
Feb 18, 2025
seisman
added
final review call
seisman
removed
the
final review call
This was referenced Feb 19, 2025
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.
Upload pygmt-docs.zip and pygmt-docs.pdf as release assets when making a release.
I tried to commit the same changes into the main branch of my own fork (seisman@bba01b4) and made a dummy v0.99.9 release at https://github.com/seisman/pygmt/releases/tag/v0.99.9. The two files were uploaded as release assets successfully.
Addressing #3731 and #1606.