-
Notifications
You must be signed in to change notification settings - Fork 32
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
Upload docs build in CI #314
Conversation
@@ -37,6 +37,13 @@ jobs: | |||
shell: bash | |||
run: | | |||
tox -edocs | |||
- name: Upload docs artifact | |||
if: always() |
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.
Any reason you like the if statement here?
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.
Like, where it is visually located? I copied the style you used from the Deploy docs
job below it
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 we can just remove the if statement here
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.
We've found it useful to set if: always
. When the Sphinx doc build fails due to warnings (e.g. bad indentation), it still produces the docs artifact. It is useful to be able to look at those docs to understand Sphinx's notoriously cryptic error messages.
Can you give an example of a use case? Is this artifact only useful for PRs, or is it useful for all docs builds? EDIT: I am starting to understand more. The |
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.
LGTM thanks 👍
I'll let @garrison take a look before approving
Yeah, it's useful for all CI builds. And there is little downside to this PR other than the couple lines of extra code. The upload should be fast and your docs are only 25MB. Concrete example: we make a big styling change in #313. I want to make it easy for us all to see what the new docs will look like, without making you build the docs locally. |
Co-authored-by: Jim Garrison <[email protected]>
This is useful to iterate on docs and debug CI issues.
The artifact will be uploaded to GitHub Actions like this: