enhance: render documents upon release (tag) #35
Closed
Conversation
This file contains 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
Publish rendered documents in HTML and PDF as release artifacts.
It is to be seen where the source documents are stored when this is integrated in [OCamlbuild](/gasche/ocamlbuild) directly. Remove logic which assumes they are in `docs/`, since that breaks the paths to included files in [`manual.adoc`](manual.adoc). Also: fix: repo name
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.
When a branch gets tagged, publish the manual rendered in HTML and PDF as release artifacts on GitHub.
Also version manual files both in their file name and title.
Work to be done by maintainer @gasche:
gasche/ocamlbuilddirectly) to Travis CI.$DEPLOY_OAUTH_TOKENhere.I've tested this and it works for me, but I haven't yet done the setup using
$DEPLOY_OAUTH_TOKEN.