chore: add codeowners for recipes folder

[tedzhouhk]

Overview:

Details:

Where should the reviewer start?

Related Issues: (use one of the action keywords Closes / Fixes / Resolves / Relates to)

• closes GitHub issue: #xxx

Summary by CodeRabbit

• Chores
  • Updated repository ownership assignments.
  • Added designated owners for the recipes content area.
  • Expanded ownership coverage to include legal and policy documents maintained by the organization.
  • Centralized responsibility for updates across relevant sections of the repository.
  • No user-facing changes or functionality impacts.

[coderabbitai]

Walkthrough

Updates the CODEOWNERS file to assign owners for the /recipes/ directory and to add ownership for several repository legal and governance files. No source code or public exports were changed.

Changes

Cohort / File(s)	Summary
Recipes ownership CODEOWNERS	Adds owners @biswapanda and @tedzhouhk for the /recipes/ directory.
Legal and governance files ownership CODEOWNERS	Assigns @ai-dynamo/Devops as owners for ATTRIBUTIONS-Rust.md, ATTRIBUTIONS.md, CODE_OF_CONDUCT.md, CONTRIBUTING.md, LICENSE, SECURITY.md.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• chore: Update CODEOWNERS, adding PeaBrane to some examples subdirs #1682 — Also modifies CODEOWNERS to add directory-specific owners for example subdirectories.
• chore: add hhzhang16 to py codeowner #2529 — Adjusts CODEOWNERS entries to add different owners to various paths.
• chore: Add Richard Huo to CODEOWNERS, and add TRTLLM section #1311 — Updates CODEOWNERS for specific directories (/container/, /examples/tensorrt_llm/).

Poem

In the burrow of files where carrots are kept,
New owners were marked while the repo slept.
Recipes get chefs, legal gets guards—
A tidy warren with well-posted cards.
Thump-thump! says the rabbit, “Ownership set!” 🥕

Pre-merge checks

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description Check	⚠️ Warning	The PR description contains the required template headings but all sections are left as placeholder text and do not describe what was changed, which files were modified, which owners were added, or why the change was made; the Related Issues line also uses a placeholder "#xxx". Because the template fields are not populated with concrete information, the description is incomplete and insufficient for a thorough review.	Please populate the template sections with concrete details: in Overview summarize the change (e.g., added CODEOWNERS entries for /recipes/ and updated CODEOWNERS for legal files), in Details list the exact files and the owner handles added or changed, and in "Where should the reviewer start?" point reviewers to the CODEOWNERS file path and relevant line ranges. Replace the placeholder Related Issues entry with the actual issue number or remove it if none exists, and add any rationale, impact notes, and testing or rollout considerations to help reviewers assess risk.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The PR title "chore: add codeowners for recipes folder" succinctly and accurately describes the primary change — adding CODEOWNERS entries for the recipes directory. It is concise, follows a conventional "chore" prefix, and will be clear to teammates scanning history. While the changes also touch legal-related CODEOWNERS entries, the title's focus on the recipes folder is acceptable because titles need not enumerate every minor additional edit.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

• Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
• Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.

---

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

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

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

CODEOWNERS (1)

34-37: Consider adding a fallback team owner for resilience.

If both individual owners are unavailable, PRs touching /recipes/ could stall. Recommend appending an existing team (e.g., @ai-dynamo/Devops) as backup.

-/recipes/ @biswapanda @tedzhouhk
+/recipes/ @biswapanda @tedzhouhk @ai-dynamo/Devops

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between dcf55c3 and aedafb8.

📒 Files selected for processing (1)

• CODEOWNERS (1 hunks)

⏰ 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: Build and Test - dynamo

🔇 Additional comments (1)

CODEOWNERS (1)

36-37: OK — /recipes/ is top-level and contains no .py files, so Python ownership won’t change.

Verification: /recipes/ exists at the repo root and no *.py files were found under it.

[grahamking]

Make it @ai-dynamo/python-codeowners @ai-dynamo/Devops so it's easier to manage, and Ops can unblock us in an emergency.