Force Storybook build publish - #3051
Closed
rajsite wants to merge 2 commits into
Closed
Conversation
Member
Author
|
Aww dang, doesn't look like forceRebuild worked :( |
Member
Author
|
Created a sb issue: chromaui/chromatic-cli#1472 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pull Request
🤨 Rationale
It was found that storybook had a behavior change where if turbosnap is enabled and no turbosnap changes are found then chromatic skipped publishing the new storybook build altogether, see example log that only had changes to example apps:
See PR discussion where behavior was noted and see discussion that first attempted to address the behavior.
👩💻 Implementation
🧪 Testing
✅ Checklist