Use AWS Amplify to deploy PRs#3133
Conversation
|
🕸 Website previewYou can view a preview here (commit |
There was a problem hiding this comment.
Pull request overview
This PR updates the Storybook GitHub Actions workflow to deploy Storybook previews to AWS Amplify (including per-PR preview URLs) and to clean up Amplify branches when PRs close.
Changes:
- Replaces Azure Static Web Apps deployment with an AWS Amplify deployment flow (create branch/deployment, upload ZIP, start deployment).
- Posts the Amplify preview URL back to the pull request as a comment.
- Updates the cleanup job to delete the corresponding Amplify branch on PR close.
🕸 Storybook previewYou can view a preview here (commit |
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 5 out of 5 changed files in this pull request and generated 5 comments.
Comments suppressed due to low confidence (1)
.github/workflows/website.yml:65
- This workflow still deploys PR previews (and cleanup) via Azure Static Web Apps. Since this PR is titled "Use AWS Amplify to deploy PRs" and closes #3094 (which aims to move away from Azure preview environment limits), consider migrating the Website preview job to Amplify as well (or update the PR scope/title/issue closure so it doesn't imply the Website has been migrated).
node-version: 24
cache: 'yarn'
- run: yarn install --immutable
- run: NODE_ENV=production yarn website
- uses: azure/static-web-apps-deploy@v1
🕸 Preview deploys |
Closes #3094
Changes
Storybook (
storybook.yml)storybook-{PR number}branches on Amplifymainbranch pushes to themainAmplify branchenvblock; referencesecretsdirectly in stepsWebsite (
website.yml)website-{PR number}branches on Amplifymainpush)Shared PR comment
### 🕸 Preview deploys)edit-mode: replacewith body reconstruction)Housekeeping (all workflows)
CHROMATIC_PROJECT_TOKENfromci.ymlenvFIGMA_TOKENfromci.yml,chromatic.yml, andrelease.ymlenvchromatic.ymlandci.ymlci.ymlNew secrets required
AWS_ACCESS_KEY_IDAWS_SECRET_ACCESS_KEYAWS_REGIONAWS_AMPLIFY_APP_ID