Skip to content

docs: never link upstream from internal PRs, issues or commits - #51

Merged
zackees merged 1 commit into
mainfrom
docs/no-upstream-links
Oct 1, 2026
Merged

zackees merged 1 commit into
mainfrom
docs/no-upstream-links

Conversation

@zackees

@zackees zackees commented Oct 1, 2026

Copy link
Copy Markdown
Owner

Policy update.

  • Internal PRs, issues, comments and commit messages never link upstream. GitHub turns each such link into a permanent "mentioned this" entry in the upstream PR's timeline, which the maintainers see, and editing the text afterwards doesn't remove it. Refer to upstream items in plain text, e.g. "upstream PR 2634".
  • Internal items may reference zackees/wild items freely.
  • Upstream PRs may link other upstream items, never fork items.
  • Applied in AGENTS.md (new "Cross-repository links" section), HOW_TO_PR_UPSTREAM.md (rule in section 5; upstream references rewritten as plain text) and the pr-upstream skill (a link-check step before approval).

Internal zackees/wild PRs, issues, comments and commit messages must not link to
upstream items. GitHub records each link as a permanent mention in the upstream
timeline, and editing the text afterwards doesn't remove it. Upstream items are
referred to in plain text ("upstream PR 2634"). Internal items may reference
zackees/wild freely; upstream PRs may link other upstream items, never fork items.
The guide and the pr-upstream skill now say the same, and the guide's upstream
references are plain text.
@zackees
zackees merged commit 93acab5 into main Oct 1, 2026
28 checks passed
@zackees
zackees deleted the docs/no-upstream-links branch October 1, 2026 02:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant