Added datadog sponsorship notice

[goruha]

what

• Added datadog sponsorship notice

Summary by CodeRabbit

• Documentation
  • Added a Sponsorship section highlighting Datadog’s support through the Open Source Program.
  • Included dark/light mode branding, a right-aligned image, and a visual divider.
  • Described availability of a Datadog-provided sandbox for automated testing and reliability improvements.
  • Applied content and formatting enhancements across user-facing docs.
  • No functional changes to the application.

[coderabbitai]

Walkthrough

Added a Sponsorship section across README files, introducing Datadog branding with dark/light logos, a sponsorship note, details about a sandbox account for automated testing, and a divider. No code or behavior changes; documentation-only updates.

Changes

Cohort / File(s)	Summary of changes
Docs — Sponsorship section README.md, README.yaml, src/README.md	Added Datadog sponsorship section with dark/light logo imagery, right-aligned inline image, sponsorship attribution, sandbox/testing description, and a horizontal divider. Purely content/formatting; no functional changes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

A rabbit taps the README drum,
New logos glow—dark, then light—how yum! 🐇✨
Datadog paws in, a friendly nod,
A sandbox burrows through our sod. 🐾
No code was moved, yet stars align—
Docs now sparkle, neat and fine.

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The title “Added datadog sponsorship notice” accurately and succinctly describes the primary change—adding a sponsorship notice for Datadog—without extraneous detail, making it clear to reviewers what was introduced in the pull request.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch datadog-oss

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 2714139 and 61f6600.

📒 Files selected for processing (3)

• README.md (1 hunks)
• README.yaml (1 hunks)
• src/README.md (1 hunks)

🧰 Additional context used

📓 Path-based instructions (3)

**/*.{yml,yaml,md}

📄 CodeRabbit inference engine (AGENTS.md)

Use 2-space indentation in YAML and Markdown files

Files:

• src/README.md
• README.yaml
• README.md

README.yaml

📄 CodeRabbit inference engine (AGENTS.md)

Treat README.yaml as the authoritative source for generating README.md (via atmos + terraform-docs)

Files:

• README.yaml

README.md

📄 CodeRabbit inference engine (AGENTS.md)

Do not manually edit README.md; regenerate it from README.yaml using atmos docs generate readme

Files:

• README.md

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: Summary

🔇 Additional comments (3)

src/README.md (1)

16-31: LGTM! Clean documentation addition.

The Sponsorship section is well-formatted with responsive dark/light mode image variants and clearly communicates Datadog's support. The content appropriately acknowledges the sandbox environment used for testing.

README.yaml (1)

11-27: LGTM! Correct source file for documentation changes.

The sponsorship content is properly added to README.yaml, which is the authoritative source per coding guidelines. The markdown formatting is clean, indentation follows the 2-space guideline, and the responsive image syntax is correct.

As per coding guidelines.

README.md (1)

39-54: Confirm README.md was regenerated from README.yaml
CI couldn’t verify because the atmos CLI isn’t installed. Please install Atmos (https://atmos.tools/install), run

atmos docs generate readme

and ensure README.md exactly matches the generated output (git diff README.md must be empty).

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🧪 Early access (Sonnet 4.5): enabled

We are currently testing the Sonnet 4.5 model, which is expected to improve code review quality. However, this model may lead to increased noise levels in the review comments. Please disable the early access features if the noise level causes any inconvenience.

Note:

• Public repositories are always opted into early access features.
• You can enable or disable early access features from the CodeRabbit UI or by updating the CodeRabbit configuration file.

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

These changes were released in v1.535.9.