Skip to content

Conversation

@helenefav
Copy link
Contributor

What does this PR do? What is the motivation?

Merge instructions

Merge readiness:

  • Ready for merge

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

@helenefav helenefav added the tap Issues created from the Tickets Analysis Platform (TAP) dashboard label Dec 4, 2025
@helenefav helenefav requested a review from a team as a code owner December 4, 2025 14:15
@github-actions github-actions bot added the Guide Content impacting a guide label Dec 4, 2025
@github-actions
Copy link
Contributor

github-actions bot commented Dec 4, 2025

Preview links (active after the build_preview check completes)

Modified Files

@rtrieu rtrieu added the editorial review Waiting on a more in-depth review label Dec 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

editorial review Waiting on a more in-depth review Guide Content impacting a guide tap Issues created from the Tickets Analysis Platform (TAP) dashboard

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants