-
Notifications
You must be signed in to change notification settings - Fork 33
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
Deploy the documentation of the main branch #818
Conversation
Alt-Ergo 2.5.0 is on opam! |
Are we sure we want to use |
Why do you want to keep old documentations here? Users can run |
It is a good practice to provide access to the documentation for all released versions (or recent-ish released versions) for users that do not use the latest release and do not have the sources readily available and want to access the documentation corresponding to their version of Alt-Ergo. Moreover, the Sphinx documentation that is built by the GH pages is not available through We used to have old versions (at least one) of the documentation, but the link to the doc for version 2.4.0 seems to be broken: https://ocamlpro.github.io/alt-ergo/API/index.html (As an aside: OPAM is able to provide docs, see e.g. https://ocaml.org/p/cmdliner/latest/doc/index.html , but it looks like ours does not get built, we should investigate this sometime as well) |
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.
After offline discussion: let's merge this and put it in 2.5.1 for now, we will figure out the issues with multiple versions later.
.github/workflows/documentation.yml
Outdated
@@ -19,7 +19,7 @@ env: | |||
jobs: | |||
# For any push and PR, build the documentation from the ocaml comments | |||
# If this build fails, the documentation workflow stops | |||
# If it succed, an artifact is made with the generated documentation | |||
# If it succeed, an artifact is made with the generated documentation |
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.
# If it succeed, an artifact is made with the generated documentation | |
# If it succeeds, an artifact is made with the generated documentation |
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.
This is an incremental spelling correction! :D
.github/workflows/documentation.yml
Outdated
@@ -95,7 +95,7 @@ jobs: | |||
|
|||
# On PR, or push on next/main, build the sphinx general documentation | |||
# If this build fails, the documentation workflow stops | |||
# If it succed, an artifact is made with the generated documentation | |||
# If it succeed, an artifact is made with the generated documentation |
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.
# If it succeed, an artifact is made with the generated documentation | |
# If it succeeds, an artifact is made with the generated documentation |
This PR should solve #693.
As soon as the opam CI accepts our packages, I will push
v2.5.x
on the branchmain
.We have to backport this patch on
v2.5.x
otherwise the documentation won't be deployed while pushing onmain
.