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
Add skipUpdateCheck
option
#928
Add skipUpdateCheck
option
#928
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice one, thanks for contributing! There's a couple tweaks that need to be made to fully support this option through all config methods (config file, CLI flag, GitHub Action arg, Node API arg). Overall looks good though 👍
Co-authored-by: Gert Hengeveld <info@ghengeveld.nl>
Co-authored-by: Gert Hengeveld <info@ghengeveld.nl>
Coverage summary from CodacySee diff coverage on Codacy
Coverage variation details
Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: Diff coverage details
Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: See your quality gate settings Change summary preferencesYou may notice some variations in coverage metrics with the latest Coverage engine update. For more details, visit the documentation |
🚀 PR was released in |
Added option (--skipUpdateCheck) to not check for an updated version of Chromatic. We have over a 100 of Storybook instances which we check with Chromatic. Our private NPM-registry-feed (Azure DevOps artifacts) does not support retrieving the version-info and triggers an error. Having these errors clutters our CI-logs.
This is a non-breaking change and can be marked as #patch