Repository navigation
ci: attach the generated Javadoc to each release - #5
Merged
Merged
Conversation
Attach the generated Javadoc of each release to that release, as a tar.gz with its checksum, so the QTSurfer website can host the reference documentation itself instead of relying on GitHub Pages. The new reference-docs workflow runs after the job that creates the GitHub Release (see ci.yml) and can also be started by hand with the tag of a release that already exists. The existing Pages job is untouched.
This branch was successfully deployed
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.
Attach the generated Javadoc of each release to that release, as a tar.gz with
its checksum, so the QTSurfer website can host the reference documentation
itself instead of relying on GitHub Pages.
The new reference-docs workflow runs after the job that creates the GitHub
Release (see ci.yml) and can also be started by hand with the tag of a release
that already exists. The existing Pages job is untouched.