-
Notifications
You must be signed in to change notification settings - Fork 706
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
feat: Publishes mdbook to Github Pages #4343
Conversation
b750dcf
to
f0d7d4f
Compare
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 sort of arbitrarily chose to do this site update when a PR is merged, rather than each time a PR is updated. I just don't think we need that much fidelity for documentation changes, but I'm open to other opinions.
This is reasonable and how were doing the others.
aws-region: us-west-1 | ||
|
||
- name: Upload to S3 | ||
if: github.event_name == 'push' || github.repository == github.event.pull_request.head.repo.full_name |
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.
right- not publishing to s3 for external forks.
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.
Much cleaner- lgtm with the caveat that we note the permissions required for docs to make it to S3.
Resolved issues:
N/A
Description of changes:
Publishes our usage guide mdbook to our github pages branch. I basically just copied s2n-quic's mdbook publish workflow, so you can find a preview of the book if you click on the github action: "book / url"
Callouts
This workflow will not run if you are opening a PR from a fork of s2n-tls. I'd rather keep s2n-tls and s2n-quic in sync than fix this problem, but it should be noted that PRs from forks won't have the preview.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.