-
Notifications
You must be signed in to change notification settings - Fork 328
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
Updates workflows to build & test Docusaurs. Closes #4754 #4789
Conversation
770b64d
to
56b2cd0
Compare
.github/workflows/release_next.yml
Outdated
working-directory: docs | ||
|
||
- name: Deploy to GitHub Pages | ||
uses: peaceiris/actions-gh-pages@v3 |
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.
Is there no github-owned package for publishing pages?
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.
Didn't find anything simular directly. Docusaurus suggests to work with this popular third-party deployment action
https://github.com/peaceiris/actions-gh-pages#%EF%B8%8F-docusaurus
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.
How about this? https://github.com/actions/deploy-pages
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.
Nice find. That appears to work as well 😄
https://github.com/Jwaegebaert/cli-build-test/actions/runs/4779137491
Although it looks like it doesn't create a commit to the branch gh-pages
. Is that common behavior for GitHub action deploys to pages?
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.
Good question. Let's find out
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.
Instead of deploying the build to a separate branch, they do a deployment to a GitHub Environement. https://github.com/Jwaegebaert/cli-build-test/deployments
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.
Just to clarify: that's sufficient for our purposes, right? I can see the docs on your repo just fine (excl. the mismatched URL but that's deliberate) but not sure if that's from a previous deployment or not.
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.
That should be sufficient enough. My docs is just because of the quick setup 😅
054fe2e
to
686e8b9
Compare
35c2f31
to
4a06416
Compare
@waldekmastykarz can I assign this one to you since you already did a review? Also I think you are more experienced with GH pipelines than I am 😄 |
4531b0d
to
19cd0da
Compare
535717e
to
c98f9fe
Compare
19cd0da
to
47e1cc2
Compare
c98f9fe
to
859c10e
Compare
47e1cc2
to
a896c04
Compare
859c10e
to
c481ae9
Compare
a896c04
to
53b0bd4
Compare
c481ae9
to
d510b9f
Compare
53b0bd4
to
c215a9b
Compare
d510b9f
to
cfc1f13
Compare
0ccf65e
to
b5b7244
Compare
cfc1f13
to
d41c4b2
Compare
d41c4b2
to
63fad98
Compare
b5b7244
to
79747ba
Compare
63fad98
to
6d7bc90
Compare
79747ba
to
68e9799
Compare
68e9799
to
bc88a8f
Compare
6d7bc90
to
57ae2da
Compare
Closes #4754