ci: fix CODEOWNERS groups

[willkill07]

Overview

Fixes the group names for CODEOWNERS.

Groups must start with @nvidia/

• I confirm this contribution is my own work, or I have the right to submit it under this project's license.
• I searched existing issues and open pull requests, and this does not duplicate existing work.

Details

N/A

Where should the reviewer start?

N/A

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

• Closes [Bug]: CODEOWNERS file is invalid #8

Summary by CodeRabbit

• Chores
  • Updated internal code review ownership assignments for repository files.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Enterprise

Run ID: 57ede289-59f2-448c-a923-ebbcfd01ea68

📥 Commits

Reviewing files that changed from the base of the PR and between 6f3ae5e and a1c6d54.

📒 Files selected for processing (1)

• .github/CODEOWNERS

📜 Recent review details

🧰 Additional context used

📓 Path-based instructions (2)

{.github/**,*.patch,**/*.sh,**/Makefile,**/*.yml,**/*.yaml}

📄 CodeRabbit inference engine (.agents/skills/rename-surfaces/SKILL.md)

Update patch files and CI scripts to reference the new names in coordinated rename operations

Files:

• .github/CODEOWNERS

{.github/**,.gitlab-ci.yml,.pre-commit-config.yaml,justfile,scripts/**}

⚙️ CodeRabbit configuration file

{.github/**,.gitlab-ci.yml,.pre-commit-config.yaml,justfile,scripts/**}: Review automation changes for reproducibility, pinned versions where appropriate, secret handling, and consistency with the documented validation matrix.
Pay attention to commands that need generated native artifacts, FFI libraries, or platform-specific environment variables.

Files:

• .github/CODEOWNERS

🔇 Additional comments (2)

.github/CODEOWNERS (2)

5-5: Default CODEOWNERS mapping is correctly normalized.

The default owner now uses fully qualified team syntax and matches the stated fix for invalid CODEOWNERS entries.

As per coding guidelines, "Update patch files and CI scripts to reference the new names in coordinated rename operations".

---

8-9: Dependency ownership rules are consistently fixed.

All dependency/lockfile rules were updated to the same @nvidia/... team namespace, which is internally consistent and aligned with the CI/approval workflow goal.

As per coding guidelines, "Update patch files and CI scripts to reference the new names in coordinated rename operations".

Also applies to: 11-12, 14-15

---

Walkthrough

Updates GitHub CODEOWNERS team references to use NVIDIA organization prefix. The default ownership entry and dependency approval entries are updated from unqualified team names to @nvidia/ prefixed team names, fixing an invalid configuration.

Changes

Cohort / File(s)	Summary
CODEOWNERS Configuration .github/CODEOWNERS	Updated team references: @nat-developers → @nvidia/nat-developers for default ownership; @nat-dep-approvers → @nvidia/nat-dep-approvers for dependency lockfile ownership across Cargo.toml, Cargo.lock, pyproject.toml, uv.lock, package.json, and package-lock.json.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title follows Conventional Commits format with type 'ci', scope absent, and concise imperative summary under 72 characters without trailing period.
Description check	✅ Passed	The description includes all required sections from the template with a clear overview, confirmation checkboxes, and issue reference, though some sections contain 'N/A'.
Linked Issues check	✅ Passed	The PR directly addresses issue #8 by fixing invalid CODEOWNERS group names to use the required '@nvidia/' prefix format, restoring file validity.
Out of Scope Changes check	✅ Passed	All changes are scoped to the CODEOWNERS file with updates to group mappings, directly addressing the invalid file format issue without extraneous modifications.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Review rate limit: 9/10 reviews remaining, refill in 6 minutes.}

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