Skip to content

Conversation

@lee-brian
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

@lee-brian lee-brian requested a review from a team as a code owner November 18, 2025 13:30
@evazorro evazorro self-assigned this Nov 18, 2025
@joepeeples
Copy link
Contributor

CI checks are hanging because the branch name doesn't follow the <name>/<description> convention as noted in the PR template, but we can override and merge because this is such a minor change.

@joepeeples joepeeples merged commit 02539cd into master Nov 18, 2025
16 of 20 checks passed
@joepeeples joepeeples deleted the lee-brian-patch-4 branch November 18, 2025 20:29
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.

4 participants