-
Notifications
You must be signed in to change notification settings - Fork 142
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
chore: update example gallery #6700
Conversation
DCO Assistant Lite bot: Thanks for your submission! We ask that you sign our Developer Certificate of Origin before we can accept your contribution. You can sign the DCO by adding a comment below using this text: I have read the DCO document and I hereby sign the DCO. github-merge-queue seems not to be a GitHub user. You need a GitHub account to be able to sign the DCO. If you have already a GitHub account, please add the email address used for this commit to your account. |
✅ Deploy Preview for carbon-for-ibm-products ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for ibm-products-web-components ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #6700 +/- ##
==========================================
+ Coverage 80.69% 80.71% +0.01%
==========================================
Files 397 397
Lines 12940 12940
Branches 4291 4291
==========================================
+ Hits 10442 10444 +2
+ Misses 2498 2496 -2
|
Closing this one — @matthewgallo (possibly serendipitously) opened a fix in #6722 that may resolve the DCO issue as well. |
This PR was automatically generated to update provided examples.
The goal is to keep our examples up-to-date with the latest changes from our own package.
What did you change?
This action ran
yarn update-gallery-config
to update examples as necessary.How did you test and verify your work?
This PR should only be merged reviewing the following checks:
yarn ci-check
runs cleanly and all tests pass.