Skip to content

Conversation

@mvillalobos418
Copy link
Contributor

corrected numbering that was previously 1,2,4 when it should be 1,2,3

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

corrected numbering that was previously 1,2,4 when it should be 1,2,3
@mvillalobos418 mvillalobos418 requested a review from a team as a code owner November 10, 2025 20:32
@cswatt cswatt merged commit b95e8e2 into master Nov 11, 2025
19 of 21 checks passed
@cswatt cswatt deleted the mvillalobos418-patch-3 branch November 11, 2025 00:27
dussault-antoine pushed a commit that referenced this pull request Nov 13, 2025
corrected numbering that was previously 1,2,4 when it should be 1,2,3
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.

3 participants