Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 7268e3d059
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| --- | ||
| title: Getting Started with Feature Flag Data in RUM | ||
|
|
||
| beta: true | ||
| description: Learn how to set up RUM to capture feature flag data and analyze the performance in Datadog | ||
| aliases: | ||
| - /real_user_monitoring/guide/getting-started-feature-flags/ | ||
| further_reading: |
There was a problem hiding this comment.
Preserve a single owner for the retired guide URLs
Deleting this page makes /real_user_monitoring/guide/setup-feature-flag-data-collection/ and /real_user_monitoring/guide/getting-started-feature-flags/ depend entirely on aliases, but both content/en/real_user_monitoring/feature_flag_tracking/setup.md:5-7 and content/en/real_user_monitoring/feature_flag_tracking/using_feature_flags.md:5-7 still claim those exact paths. Hugo only writes one alias file per path, so after this removal existing bookmarks and in-product links to the legacy guide can land on whichever of the two pages is rendered last instead of a deterministic replacement.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Codex is right! setup.md and using_feature_flags.md have duplicate aliases that should be deduped.
|
The rest of the changes look good! |
urseberry
left a comment
There was a problem hiding this comment.
I'm leaving a comment on the file view to get the PR out of the review queue.
What does this PR do? What is the motivation?
Finishes the consolidation started in #25073 by adding the missing Kameleoon integration to the Feature Flag Tracking setup page and removing the old guide page it was left behind in.
/real_user_monitoring/feature_flag_tracking/setup/guide/setup-feature-flag-data-collection.md(content now fully consolidated into the setup page; old URL redirects via existing alias)_index.md,using_feature_flags.md, andbrowser/troubleshooting.mdto point to the setup pageMerge instructions
Merge readiness:
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.
AI assistance
Additional notes