Skip to content

[no-ci] docs: instruct agents to use personal fork, not upstream, for PRs #2191

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
mdboom merged 3 commits into from
Jun 11, 2026
Merged

[no-ci] docs: instruct agents to use personal fork, not upstream, for PRs #2191

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
cf024fb
docs: instruct agents to use personal fork, not upstream, for PRs
mdboom Jun 10, 2026
1569a10
Apply suggestion from @mdboom
mdboom Jun 11, 2026
6dce0e7
Merge branch 'main' into dont-create-branches-on-fork
mdboom Jun 11, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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).

@leofang leofang Jun 11, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: upstream is not a "fork" I think, maybe replace it by "repo"?

Comment thread
mdboom marked this conversation as resolved.
Outdated
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 <personal-fork-remote> <branch>`). 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
Expand Down
Loading