From cf024fb0a7ef9ec2232381f1725524aa741637eb Mon Sep 17 00:00:00 2001 From: Michael Droettboom Date: Wed, 10 Jun 2026 10:36:12 -0400 Subject: [PATCH 1/2] docs: instruct agents to use personal fork, not upstream, for PRs Co-Authored-By: Claude Sonnet 4.6 --- AGENTS.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/AGENTS.md b/AGENTS.md index a4450fbc664..4ec2eb49ebd 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -14,6 +14,14 @@ guide for package-specific conventions and workflows. # Pull requests +**Never push branches or commits to the upstream fork (github.com/NVIDIA/cuda-python). +Treat it as read-only.** All branch creation and pushes must go to the contributor's +personal fork. Before pushing, confirm which remote points to the contributor's +personal fork (not `upstream`) by running `git remote -v`, then push there +(`git push `). Open the PR from that fork with +`gh pr create`. Do not use `git push upstream` or any command that writes to +the `upstream` remote. + When creating pull requests with `gh pr create`, always assign at least one label and a milestone. CI enforces this via the `pr-metadata-check` workflow and will block PRs that are missing labels or a milestone. Use `--label` and From 1569a10b8e0ff197d437b02c001c267f19a444ba Mon Sep 17 00:00:00 2001 From: Michael Droettboom Date: Thu, 11 Jun 2026 09:14:16 -0400 Subject: [PATCH 2/2] Apply suggestion from @mdboom --- AGENTS.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/AGENTS.md b/AGENTS.md index 4ec2eb49ebd..7e1582761b7 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -14,7 +14,7 @@ guide for package-specific conventions and workflows. # Pull requests -**Never push branches or commits to the upstream fork (github.com/NVIDIA/cuda-python). +**Never push branches or commits to the upstream repo (github.com/NVIDIA/cuda-python). Treat it as read-only.** All branch creation and pushes must go to the contributor's personal fork. Before pushing, confirm which remote points to the contributor's personal fork (not `upstream`) by running `git remote -v`, then push there