Skip to content
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

[No QA] Proceed with web deploy even if storybook build fails #9795

Merged
merged 1 commit into from
Jul 8, 2022

Conversation

roryabraham
Copy link
Contributor

@roryabraham roryabraham commented Jul 8, 2022

Details

This ensures that the web deploy will continue even if the storybook build step fails.

Fixed Issues

$ #9782

Tests

The only testing I did was a POC here with this PR, but that gives me enough confidence to assume that this will work as expected.

@roryabraham roryabraham self-assigned this Jul 8, 2022
@roryabraham roryabraham marked this pull request as ready for review July 8, 2022 06:28
@roryabraham roryabraham requested a review from a team as a code owner July 8, 2022 06:28
@melvin-bot melvin-bot bot requested review from arosiclair and removed request for a team July 8, 2022 06:29
@arosiclair arosiclair merged commit e793fe8 into main Jul 8, 2022
@arosiclair arosiclair deleted the Rory-StorybookDontBreakWebBuilt branch July 8, 2022 13:32
@OSBotify
Copy link
Contributor

OSBotify commented Jul 8, 2022

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

@OSBotify
Copy link
Contributor

🚀 Deployed to staging by @arosiclair in version: 1.1.83-1 🚀

platform result
🤖 android 🤖 success ✅
🖥 desktop 🖥 success ✅
🍎 iOS 🍎 success ✅
🕸 web 🕸 success ✅

@OSBotify
Copy link
Contributor

🚀 Deployed to production by @chiragsalian in version: 1.1.84-13 🚀

platform result
🤖 android 🤖 success ✅
🖥 desktop 🖥 success ✅
🍎 iOS 🍎 success ✅
🕸 web 🕸 success ✅

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants