Skip to content

chore(codeowners): add global router team as co-owner of workspace Cargo.toml and Cargo.lock - #17522

Open
sachalmalick wants to merge 1 commit into
mainfrom
claude/global-router-cargo-config-z85ea0
Open

sachalmalick wants to merge 1 commit into
mainfrom
claude/global-router-cargo-config-z85ea0

Conversation

@sachalmalick

@sachalmalick sachalmalick commented Oct 28, 2026 •

Copy link
Copy Markdown
Contributor

Overview

Global Router work (e.g. #17355, #17208) keeps touching the workspace Cargo.toml and Cargo.lock to add crates and dependencies. Today those two files are owned by @ai-dynamo/dynamo-ops-codeowners alone, so every such change waits on ops. This PR adds @ai-dynamo/dynamo-global-router-codeowners as a co-owner of both, following the same shared: co-ownership approach used to add the sidecar team (#16826).

Key Changes

  • .github/codeowners/areas.yaml: new shared entries for Cargo.lock and Cargo.toml with owners ops + global-router (ops kept).
  • CODEOWNERS: regenerated with emit_codeowners.py, not hand-edited.

Under the "any one approves" rule, either team can now approve changes to these files.

Validation

  • build_codeowners.py --strict passes.
  • emit_codeowners.py output is committed.
  • who_owns.py Cargo.toml Cargo.lock shows @ai-dynamo/dynamo-ops-codeowners @ai-dynamo/dynamo-global-router-codeowners.

Issues and Ongoing Work

  • No tracking issue yet. One still needs to be linked for the PR Issue Link check.
Pull Request Checklist
  • I used Dynamo's /pr-checklist skill.

Generated by Claude Code

Summary by CodeRabbit

  • Chores
    • Updated maintenance ownership for project dependency configuration files. This administrative change does not alter product functionality or affect the user experience.

…rgo files

Global Router crate and dependency changes touch the workspace Cargo.toml
and Cargo.lock, which are owned by ops alone. Add global-router as a
co-owner (ops kept), mirroring how sidecar was added as a co-owner of
its shared paths, so the global router team can approve those changes
without waiting on ops.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016XAk4nodBkjw1fYrFr9b3x
Signed-off-by: Claude <noreply@anthropic.com>
@sachalmalick
sachalmalick requested review from a team as code owners October 28, 2026 17:37
@copy-pr-bot

copy-pr-bot Bot commented Oct 28, 2026

Copy link
Copy Markdown

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

@coderabbitai

coderabbitai Bot commented Oct 28, 2026

Copy link
Copy Markdown
Contributor

Review in Change Stack →

No actionable comments were generated in the recent review.

Recent review info
Run configuration
Commits

Reviewing files that changed from the base of the PR and between 843dc32 and 87b3fcf.

Files selected for processing: 2
  • .github/codeowners/areas.yaml
  • CODEOWNERS

Included review availability: This review used your included allowance. Your plan provides up to 12 included reviews per hour; 10 remain after this review.

Walkthrough

The ownership configuration assigns both ops and global-router to the Cargo manifest and lockfile.

Changes

Cargo File Ownership

Layer / File(s) Summary
Shared Cargo ownership rules
.github/codeowners/areas.yaml, CODEOWNERS
Both ownership configuration files assign the Cargo manifest and lockfile to ops and global-router.

Priority: Low

Estimated code review effort: 1 (Trivial) | ~3 minutes

Merge Risk: Minimal · up to 87b3f

No actionable merge-blocking risk is evident in this ownership-only change.

Pre-merge checks: Passed 5
Check name Status Explanation
Title check Passed The title clearly states the main change: adding the Global Router team as a co-owner of the workspace Cargo.toml and Cargo.lock files.
Description check Passed The description includes all required sections and explains the ownership change, generated-file update, validation steps, and outstanding issue-link status. The checklist remains unchecked and no tra…
Docstring Coverage Passed No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentat…
Linked Issues check Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check Passed Check skipped because no linked issues were found for this pull request.
Full details: Description check

Explanation

The description includes all required sections and explains the ownership change, generated-file update, validation steps, and outstanding issue-link status. The checklist remains unchecked and no tracking issue is linked, but these omissions do not make the description incomplete.

Full details: Docstring Coverage

Explanation

No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 0 files. (2 skipped: 2 unsupported.)

  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Comment @coderabbitai help to get the list of available commands.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants