-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Fix typos in Failure to Answer docs #29354
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
base: master
Are you sure you want to change the base?
Conversation
What's the reason I was tagged on this pull request? Rosa's approval applies for the documentation team. My approval shouldn't be needed. You are free to use the merge command and merge this PR. |
/merge |
View all feedbacks in Devflow UI.
This merge request is not mergeable yet, because of pending checks/missing approvals. It will be added to the queue as soon as checks pass and/or get approvals.
devflow unqueued this merge request: It did not become mergeable within the expected time |
/merge |
View all feedbacks in Devflow UI.
PR already in the queue with status waiting |
/merge |
View all feedbacks in Devflow UI.
This merge request is not mergeable yet, because of pending checks/missing approvals. It will be added to the queue as soon as checks pass and/or get approvals.
devflow unqueued this merge request: It did not become mergeable within the expected time |
/merge |
View all feedbacks in Devflow UI.
This merge request is not mergeable yet, because of pending checks/missing approvals. It will be added to the queue as soon as checks pass and/or get approvals.
devflow unqueued this merge request: It did not become mergeable within the expected time |
@mtullalizardi I noticed we seemed to have some issues merging this PR! That's because your branch name doesn't have a slash in it, which is important for our automations to run. The easiest way around this is typically to close your PR, rename your branch to fulfill the requirements we list in the "For Datadog employees" section above, and then open a new one. Then we can get this approved and published using those automations. Sorry for the inconvenience, and let us know if you have any questions! |
What does this PR do? What is the motivation?
Merge instructions
Merge readiness:
For Datadog employees:
Merge queue is enabled in this repo. Your branch name MUST follow the
<name>/<description>
convention and include the forward slash (/
). Without this format, your pull request will not pass in 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.
To have your PR automatically merged after it receives the required reviews, add the following PR comment:
Additional notes