chore(CODEOWNERS): Use Team alias for Rust code owners

[grahamking]

Also add to examples for Rust parts.

Summary by CodeRabbit

• Chores
  • Updated code ownership assignments for Rust files and examples to a single team, simplifying and consolidating ownership.

[coderabbitai]

Walkthrough

The CODEOWNERS file was updated to consolidate Rust file and Cargo.toml ownership under a single team alias, replacing multiple individual owners. The ownership list for the /examples/ directory was also adjusted, moving the team alias to a new position and replacing an individual owner.

Changes

File(s)	Change Summary
CODEOWNERS	Consolidated Rust (*.rs, Cargo.toml) ownership to @ai-dynamo/dynamo-rust-codeowners team; reordered and replaced an individual owner with the team alias in the /examples/ directory ownership list.

Possibly related PRs

• chore: Update CODEOWNERS, adding PeaBrane to some examples subdirs #1682: Also modifies the CODEOWNERS file to update ownership assignments for example directories.
• chore(CODEOWNERS): Make *.rs and Cargo.toml lists the same #1811: Updates and consolidates CODEOWNERS assignments for Rust files and directories, focusing on team alias alignment.
• chore: Update CODEOWNERS #1380: Adjusts CODEOWNERS for Rust files and /examples/ directory, but with a different approach to structuring ownership.

Poem

In the garden of CODEOWNERS, neat and precise,
The Rusty rows now need just one team to suffice.
No more a crowd, but a single name,
To guard the code and stake their claim.
🐇 With a twitch of my nose and a hop of delight,
Ownership’s tidy—oh what a sight!

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between c5f5dd2 and 3a1e546.

📒 Files selected for processing (1)

• CODEOWNERS (2 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). (3)

• GitHub Check: Mirror Repository to GitLab
• GitHub Check: pre-commit
• GitHub Check: Build and Test - vllm

🔇 Additional comments (2)

CODEOWNERS (2)

7-8: LGTM! Excellent consolidation of Rust code ownership.

This change effectively consolidates Rust code ownership under a single team alias, which aligns perfectly with the PR objectives. The comment on line 6 even anticipated this improvement ("Or better make an alias like devops have"). This simplifies maintenance and follows the established pattern used by other teams in the file.

---

20-20: Good consistency in applying the team alias to examples.

Moving the @ai-dynamo/dynamo-rust-codeowners team alias to the middle position in the examples directory ownership list maintains consistency with the Rust code ownership consolidation. This ensures that Rust-related examples are also covered by the same team structure.

---

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

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[nnshah1]

LGTM