Feat: Add GitHub Actions workflow for deploying Storybook to GitHub Pages - #180
Conversation
There was a problem hiding this comment.
Pull Request Overview
This PR adds a GitHub Actions workflow to automatically deploy Storybook to GitHub Pages when changes are pushed to the main branch or manually triggered. The workflow builds the Storybook static site and deploys it using GitHub's Pages deployment action.
Key changes:
- Added build script to Storybook package.json for generating static output
- Created GitHub Actions workflow with build and deploy jobs for Pages deployment
Reviewed Changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| packages/apps/storybook/package.json | Added build script to generate static Storybook output |
| .github/workflows/deploy-storybook.yml | New workflow for building and deploying Storybook to GitHub Pages |
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
aruniverse
left a comment
aruniverse
left a comment
There was a problem hiding this comment.
can you review what other repos publishing storybook looks like
…g with rush in the project
I checked appui, they use JamesIves/github-pages-deploy-action@v4 to deploy which relies on creating a separate gh-pages branch and generating a commit to it every time a PR is merged. I'm using the actions/deploy-pages@v1 which is the official way to deploy artifacts to pages. It's less customizable, but easier to implement. Honestly I'm not too familiar with ci/cd, but that was just an attempt to have the storybook available to view without having to run the code, cuz that would be really helpful. |
No description provided.