We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
- Do you want to request a feature or report a bug?
This is a new feature that I'm wondering about.
- What is the current behavior?
After an incident, we organize a learning review and put the outcome in a blog post. We usually update the incident with the link to this blog post.
- What is the expected behavior?
I'm wondering if it'd be more useful to add a learning reviews section to write those outcomes here.
The text was updated successfully, but these errors were encountered:
I vote yes, but i think it should be optional since we don't even have one for all of our incidents (eg ns1 degradation)
Sorry, something went wrong.
I vote yes!
I think not. Update the incident with a link if you want to show this.
No branches or pull requests
- Do you want to request a feature or report a bug?
This is a new feature that I'm wondering about.
- What is the current behavior?
After an incident, we organize a learning review and put the outcome in a blog post. We usually update the incident with the link to this blog post.
- What is the expected behavior?
I'm wondering if it'd be more useful to add a learning reviews section to write those outcomes here.
The text was updated successfully, but these errors were encountered: