-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
docs(postmortem): add icons-angular v10.5.0 incident #3749
docs(postmortem): add icons-angular v10.5.0 incident #3749
Conversation
Deploy preview for the-carbon-components ready! Built with commit 79d55a3 https://deploy-preview-3749--the-carbon-components.netlify.com |
Deploy preview for carbon-elements ready! Built with commit 79d55a3 |
Deploy preview for carbon-components-react ready! Built with commit 79d55a3 https://deploy-preview-3749--carbon-components-react.netlify.com |
Deploy preview for the-carbon-components ready! Built with commit 3bae3d6 https://deploy-preview-3749--the-carbon-components.netlify.com |
Deploy preview for carbon-elements ready! Built with commit 3bae3d6 |
Deploy preview for carbon-components-react ready! Built with commit 3bae3d6 https://deploy-preview-3749--carbon-components-react.netlify.com |
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! just a couple notes
docs/postmortems/00-template.md
Outdated
|
||
**Summary** | ||
|
||
Ipsum culpa molestias doloribus modi veniam ipsa Voluptatem voluptatum error |
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.
maybe instead of lorem ipsum we can help people fill these sections out by providing questions or comments like in our issue and PR templates
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.
On it!
Co-Authored-By: emyarod <[email protected]>
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.
Thanks for writing this up @joshblack, and for sorting out the situation quickly 💯
Cases like this should be rare, but I wonder if there's some post-build, pre-deploy, sanity checks that would help ... in this case a general file structure validation would have been enough to trigger a warning.
Ideally this is something our upgrade tooling could catch, but we're just not there yet.
@cal-smith part of me wants to just define full end-to-end workflows with verdaccio and publish and run some kind of install check. For example, on the React side we manually use |
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 and seems like a great idea going forward! 🎉
@joshblack Whoa, that sounds fantastic ... I'll have to poke around to see how that works ... I'll be in touch haha |
Add in
postmortem
process an initial document for@carbon/icons-angular
incidentChangelog
New
README.md
forpostmortem
folder@carbon/icons-angular
Changed
on-windows-hcm-support.md
moved back todocs
post-mortems
->postmortems
Removed