Moved Code Origins content under /tracing parent instead of /guide

[sstonehill12]

What does this PR do? What is the motivation?

The Code Origins page had originally been stored under the /guides folder, but really belongs under /tracing.

Merge instructions

Merge readiness:

• Ready for merge

For Datadog employees:
Merge queue is enabled in this repo. Your branch name MUST follow the <name>/<description> convention and include the forward slash (/). Without this format, your pull request will not pass in 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.

To have your PR automatically merged after it receives the required reviews, add the following PR comment:

/merge

Additional notes

[github-actions]

Preview links (active after the build_preview check completes)

Renamed files

• https://docs-staging.datadoghq.com/sarah.stonehill/code-origins-folder-change/tracing/code_origins/

Modified Files

• https://docs-staging.datadoghq.com/sarah.stonehill/code-origins-folder-change/tracing/guide/

[estherk15]

Looks good, I added the alias for redirects since the URL changed. Let me know if you have any questions!

[sstonehill12]

/merge

[dd-devflow]

View all feedbacks in Devflow UI.

2025-05-01 13:49:26 UTC ℹ️ Start processing command /merge

---

2025-05-01 13:49:30 UTC ℹ️ MergeQueue: pull request added to the queue

The expected merge time in master is approximately 20m (p90).

---

2025-05-01 13:53:13 UTC ❌ MergeQueue: The build pipeline failed for this merge request

Build pipeline has failing jobs for b9326d3:

• build_preview_mergequeue

⚠️ Do NOT retry failed jobs directly (why?).

What to do next?

• Investigate the failures and when ready, re-add your pull request to the queue!
• If your PR checks are green, try to rebase/merge. It might be because the CI run is a bit old.
• Any question, go check the FAQ.

[sstonehill12]

Hi @estherk15! Do you know why the merge failed? Do I need to fix something before this can be merged?

[estherk15]

/merge

[dd-devflow]

View all feedbacks in Devflow UI.

2025-05-01 15:51:41 UTC ℹ️ Start processing command /merge

---

2025-05-01 15:51:48 UTC ℹ️ MergeQueue: waiting for PR to be ready

This merge request is not mergeable yet, because of pending checks/missing approvals. It will be added to the queue as soon as checks pass and/or get approvals.
Note: if you pushed new commits since the last approval, you may need additional approval.
You can remove it from the waiting list with /remove command.

---

2025-05-01 19:23:08 UTC ℹ️ MergeQueue: merge request added to the queue

The expected merge time in master is approximately 20m (p90).

---

2025-05-01 19:38:59 UTC ℹ️ MergeQueue: This merge request was merged