-
Notifications
You must be signed in to change notification settings - Fork 1.2k
INA-7891: Extract off-topic sections from "Describe incident" documentation #30917
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
Conversation
✅ Documentation Team ReviewThe documentation team has approved this pull request. Thank you for your contribution! |
Preview links (active after the
|
Thanks, @cperryk ! Created DOCS-11749 for review. |
Thanks @domalessi — Just for my awareness, roughly how long should I expect that review to take? (No pressure, just wondering.) And is this elevated level of review due to the fact that I have created a new page? |
@cperryk The "elevated" review was just because I didn't have time to review myself during my on call session yesterday! It's a relatively small PR though, so I expect turnaround time should be within a few days. If you need this by a certain date, I can certainly flag that for my team. Let me know! |
@domalessi Ah, I see, thanks! Not needed by a certain date. Appreciate the help! |
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 updating this @cperryk , left some formatting and link fixes. Let me know if you have questions. If this looks good, I can merge!
content/en/service_management/incident_management/response_team.md
Outdated
Show resolved
Hide resolved
content/en/service_management/incident_management/response_team.md
Outdated
Show resolved
Hide resolved
content/en/service_management/incident_management/response_team.md
Outdated
Show resolved
Hide resolved
content/en/service_management/incident_management/response_team.md
Outdated
Show resolved
Hide resolved
content/en/service_management/incident_management/response_team.md
Outdated
Show resolved
Hide resolved
content/en/service_management/incident_management/response_team.md
Outdated
Show resolved
Hide resolved
Co-authored-by: Esther Kim <[email protected]>
…m.md Co-authored-by: Esther Kim <[email protected]>
…m.md Co-authored-by: Esther Kim <[email protected]>
…m.md Co-authored-by: Esther Kim <[email protected]>
…m.md Co-authored-by: Esther Kim <[email protected]>
…m.md Co-authored-by: Esther Kim <[email protected]>
…m.md Co-authored-by: Esther Kim <[email protected]>
Co-authored-by: Esther Kim <[email protected]>
@estherk15 Thanks, merge away! |
What does this PR do? What is the motivation?
This PR updates Incident Management documentation to extract content from the "Describe incident" page that has nothing to do with describing the incident.
Specifically, it:
Merge instructions
Merge readiness:
For Datadog employees:
Your branch name MUST follow the
<name>/<description>
convention and include the forward slash (/
). Without this format, your pull request will not pass CI, the GitLab pipeline will not run, and you won't get a branch preview. Getting a branch preview makes it easier for us to check any issues with your PR, such as broken links.If your branch doesn't follow this format, rename it or create a new branch and PR.
[6/5/2025] Merge queue has been disabled on the documentation repo. If you have write access to the repo, the PR has been reviewed by a Documentation team member, and all of the required checks have passed, you can use the Squash and Merge button to merge the PR. If you don't have write access, or you need help, reach out in the #documentation channel in Slack.
Additional notes