chore: repoint team references to dsx-ai-factory - #1925
Draft
kristinapathak wants to merge 1 commit into
Draft
kristinapathak wants to merge 1 commit into
kristinapathak wants to merge 1 commit into
Conversation
github.com/NVIDIA/nvcf is transferring to github.com/dsx-ai-factory/nvcf (NVBug 6782495). Team access does not travel across GitHub orgs, and GitHub does not error on an unresolvable CODEOWNERS owner -- it silently stops matching, so code-owner review would quietly stop being enforced if left pointing at @NVIDIA/nvcf-* after the move. Rewrites every @NVIDIA/nvcf-* reference to @dsx-ai-factory/nvcf-*: .github/CODEOWNERS, the two subtree CODEOWNERS files, and the four AGENTS.md docs that name a default owning team. The seven dsx-ai-factory/nvcf-* teams already exist with matching membership, maintainers, and review-assignment settings, ported ahead of the move. Do not merge before the transfer completes: today, on NVIDIA/nvcf, these teams don't resolve (dsx-ai-factory teams have no access to a NVIDIA-org repo), which would either hard-block every merge or silently drop code-owner enforcement entirely -- the exact failure this change exists to prevent, just triggered early instead of avoided. Ref: NVCF-11339, nvbugspro.nvidia.com/bug/6782495
|
Important Draft PR not reviewedDraft PRs are not automatically reviewed by default.
To automatically review draft PRs, update your CodeRabbit configuration: reviews:
auto_review:
drafts: trueComment |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Rewrites every
@NVIDIA/nvcf-*team reference to@dsx-ai-factory/nvcf-*:.github/CODEOWNERS(the enforced one, 7 teams across ~35 path rules)tools/ncp-local-cluster/CODEOWNERSandsrc/compute-plane-services/ess-agent/.github/CODEOWNERS(nested, not GitHub-enforced, but stale otherwise)deploy/helm/{notary,icms,cloud-tasks}/AGENTS.mdandsrc/compute-plane-services/nvca/AGENTS.md(default-owner docs)Why
NVIDIA/nvcfis transferring todsx-ai-factory/nvcf(SCM NVBug 6782495, targeting 2026-09-18, tracked in NVCF-11339). Team access does not travel across GitHub orgs, and GitHub does not error on an unresolvable CODEOWNERS owner — it silently stops matching, so code-owner review would quietly stop being enforced if this file kept pointing at@NVIDIA/nvcf-*after the move.The seven
dsx-ai-factory/nvcf-*teams already exist with matching membership, maintainers, and review-assignment settings, ported ahead of the move.Do not merge before the transfer completes
This is opened as a draft on purpose. Today, on
NVIDIA/nvcf,dsx-ai-factoryteams don't resolve — adsx-ai-factory-org team has no access grant on aNVIDIA-org repo. Merging this now would either hard-block every PR from merging (themain protectionruleset requires code-owner approval) or silently drop enforcement entirely — the exact failure this PR exists to prevent, just triggered three days early instead of avoided. Merge this right after cutover, in the same window as the technical-inventory doc's "Sequence: after the move" step.Ref: NVCF-11339, nvbugspro.nvidia.com/bug/6782495