-
Notifications
You must be signed in to change notification settings - Fork 73
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
Re-enable GitHub Pages deploy workflow #213
Conversation
GitHub now offers an official way to deploy static site to GitHub Pages using GitHub Actions. Using an official method is preferable because we can't assume the API keeps backwards compatibility (esp. GitHub). In mid-to-long term, I believe this transition reduces future maintenance costs.
Can we test this before merging @pocka ? it LGTM. |
Merged this branch locally then pushed to my temporary fork (will remove once this PR got merged). https://github.com/pocka/addon-designs-ci-test/actions/runs/6197014978 |
This looks great! thank you so much as always @pocka <3 <3 |
It seems the deployment failed due to the existing |
@yannbf looks like you fixed it? |
@ndelangen No I did not. The deployment seems broken still. @pocka the error is as follows:
So probably the script has to run from the |
I found an issue with the exact same error message in the Action's repo:
No, ---
title: Legacy pipeline
---
flowchart LR
master["Default branch"]
action["GitHub Actions"]
ghpages["gh-pages branch"]
hosting["GitHub Pages"]
master -. Trigger .-> action
action -- Push built files --> ghpages
hosting -- Serve --> ghpages
---
title: New pipeline
---
flowchart LR
master["Default branch"]
action["GitHub Actions"]
storage["Some GitHub internal storage idk"]
hosting["GitHub Pages"]
master -. Trigger .-> action
action -- Place built files --> storage
hosting -- Serve --> storage
I don't think it has/will have better future maintanance and quality. This my impression is from glancing at README and existence of "hacktoberfest" tag on repo description. The Reading the above issue and the Action's README, changing deploy source to "GitHub Actions" from repository setting page would solve the problem. Deleting |
Thank you so much @pocka! Changing the source and removing gh-pages branch fixed it. It's now working as intended. |
This PR re-enables a GitHub Actions workflow that builds example Storybook then deploys it to GitHub Pages. I have also changed the deploy action to the new official action from third party one (5500a94).
Fix #187.