-
Notifications
You must be signed in to change notification settings - Fork 14
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
Add a github action to run doc-gen #5
base: master
Are you sure you want to change the base?
Add a github action to run doc-gen #5
Conversation
Note that we also have to bump the lean/mathlib version, as doc-gen requires a recent version. I haven't checked whether this breaks anything.
Co-authored-by: Mauricio Collares <[email protected]>
.github/workflows/lean_doc.yml
Outdated
cd doc-gen | ||
lean -v | ||
# the json and diagnostics are emitted on stdout, but the json is always the last (very long) line. | ||
lean src/entrypoint.lean > export.json || true |
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.
lean src/entrypoint.lean > export.json || true | |
lean --run src/entrypoint.lean > export.json || true |
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.
I think that's now overkill: this is what I use elsewhere:
.github/workflows/lean_doc.yml
Outdated
cd doc-gen | ||
lean -v | ||
# the json and diagnostics are emitted on stdout, but the json is always the last (very long) line. | ||
lean src/entrypoint.lean > export.json || true |
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.
I think that's now overkill: this is what I use elsewhere:
Note that we also have to bump the lean/mathlib version, as doc-gen requires a recent version.
I haven't checked whether this breaks anything.
Note that this produces a handful of errors, as you have files that define the same name in the global namespace, which makes it impossible to import these at the same time. Wrapping each file in
namespace «2021» ... end «2019»
etc would probably fix this.If you don't do that, it just means that half these definitions will be missing from the docs.