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
fix(icons): update ci-check to fail with exit code 1 #3856
fix(icons): update ci-check to fail with exit code 1 #3856
Conversation
Deploy preview for the-carbon-components ready! Built with commit 16818aa https://deploy-preview-3856--the-carbon-components.netlify.com |
Deploy preview for carbon-elements ready! Built with commit 16818aa |
Deploy preview for carbon-components-react ready! Built with commit 16818aa https://deploy-preview-3856--carbon-components-react.netlify.com |
Deploy preview for the-carbon-components ready! Built with commit facfbe0 https://deploy-preview-3856--the-carbon-components.netlify.com |
Deploy preview for carbon-components-react ready! Built with commit facfbe0 https://deploy-preview-3856--carbon-components-react.netlify.com |
Deploy preview for carbon-elements ready! Built with commit facfbe0 |
@joshblack is 2d7d006 to test that the fail working properly? |
@vpicone I think we renamed it to 3D-iCa right? It seems like our ci-check didn't pick up that we wanted to remove the asset, if we still want it totally fair! I can add back in the metadata |
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.
👍
@joshblack ah nvm Coulda sworn I renamed it properly in my PR... |
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.
looks good to me. I guess there will be a follow up PR to add that missing subcategory?
Note to reviewers, couple of TODOs left on my end:
|
…n into fix/update-icon-ci-check
Issue to update mis-categorized or misnamed icons: #3877 |
When handling our refactor, we had assumed
console.error
would setprocess.exitCode
to1
, instead theci-check
fails silently (withexitCode
as0
). This updates it so that the catch handler exits with an exit code of1
, signaling that an error has occurred and failing CI.Changelog
New
Changed
process.exit(1)
to fail with code1
Removed