Skip to content

Conversation

@domalessi
Copy link
Contributor

What does this PR do? What is the motivation?

Updates site support for the following pages:

All three should flag that features are unavailable for US1-FED.

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

@domalessi domalessi requested review from a team as code owners December 1, 2025 21:11
@github-actions github-actions bot added Architecture Everything related to the Doc backend Guide Content impacting a guide labels Dec 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Architecture Everything related to the Doc backend Guide Content impacting a guide

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants