Skip to content

Conversation

amlakhanpal
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

@amlakhanpal amlakhanpal requested a review from a team as a code owner August 29, 2025 18:09
Copy link
Contributor

Preview links (active after the build_preview check completes)

Modified Files

Co-authored-by: Ursula Chen <58821586+urseberry@users.noreply.github.com>
@urseberry urseberry merged commit 7eab10c into master Aug 29, 2025
17 of 18 checks passed
@urseberry urseberry deleted the amlakhanpal/api-docs branch August 29, 2025 21:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants