From 1b007422177caaa985c3fabd4fe1a692cb5f6088 Mon Sep 17 00:00:00 2001 From: realAsma Date: Sun, 13 Sep 2026 14:13:59 +0000 Subject: [PATCH 1/3] Document copy-PR testing authorization Signed-off-by: realAsma --- CONTRIBUTING.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index cdeb7a1dadd..b77b5e0da3f 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -264,6 +264,11 @@ nox -s "unit-3.12(torch_211, tf_latest)" ## Submitting your code - Submit a pull request and let auto-assigned reviewers (based on [CODEOWNERS](./.github/CODEOWNERS)) review your PR. +- Pull requests from forks require validation before workflows can run on NVIDIA's runners. After reviewing the + exact head commit for safe execution, an authorized vetter can start testing by commenting + `/ok to test ` on the pull request. See the copy-PR guidance for + [contributors](https://docs.gha-runners.nvidia.com/cpr/contributors) and + [vetters](https://docs.gha-runners.nvidia.com/cpr/vetters). - If any CI/CD checks fail, fix the issues and push again. - Once your PR is approved and all checks pass, one of the reviewers will merge the PR. - If your PR is a bug fix that should also land in an ongoing release branch, add the From 5c3560d8fd8783bb1068e8c9793d7869c8b8d047 Mon Sep 17 00:00:00 2001 From: realAsma Date: Sun, 13 Sep 2026 14:46:52 +0000 Subject: [PATCH 2/3] Clarify copy-PR testing approval Signed-off-by: realAsma --- CONTRIBUTING.md | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index b77b5e0da3f..ca2733642ad 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -264,11 +264,8 @@ nox -s "unit-3.12(torch_211, tf_latest)" ## Submitting your code - Submit a pull request and let auto-assigned reviewers (based on [CODEOWNERS](./.github/CODEOWNERS)) review your PR. -- Pull requests from forks require validation before workflows can run on NVIDIA's runners. After reviewing the - exact head commit for safe execution, an authorized vetter can start testing by commenting - `/ok to test ` on the pull request. See the copy-PR guidance for - [contributors](https://docs.gha-runners.nvidia.com/cpr/contributors) and - [vetters](https://docs.gha-runners.nvidia.com/cpr/vetters). +- Pull requests from forks require approval before running on NVIDIA infrastructure. An authorized vetter can + approve the current commit by commenting `/ok to test `. - If any CI/CD checks fail, fix the issues and push again. - Once your PR is approved and all checks pass, one of the reviewers will merge the PR. - If your PR is a bug fix that should also land in an ongoing release branch, add the From 998d040da2a2507e3b8f4cb1f010d8b4f7ab6a18 Mon Sep 17 00:00:00 2001 From: realAsma Date: Sun, 13 Sep 2026 15:29:56 +0000 Subject: [PATCH 3/3] Clarify CI approval paths Signed-off-by: realAsma --- CONTRIBUTING.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index ca2733642ad..f895ac1d93b 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -264,8 +264,9 @@ nox -s "unit-3.12(torch_211, tf_latest)" ## Submitting your code - Submit a pull request and let auto-assigned reviewers (based on [CODEOWNERS](./.github/CODEOWNERS)) review your PR. -- Pull requests from forks require approval before running on NVIDIA infrastructure. An authorized vetter can - approve the current commit by commenting `/ok to test `. +- **Fork PRs:** An authorized vetter must comment `/ok to test ` to run NVIDIA-hosted CI. +- **Contributors without write access:** When GitHub requests workflow approval, a reviewer with write permission + must select **Approve and run workflows** to start GitHub Actions CI. - If any CI/CD checks fail, fix the issues and push again. - Once your PR is approved and all checks pass, one of the reviewers will merge the PR. - If your PR is a bug fix that should also land in an ongoing release branch, add the