docs: warn fork authors about GitHub's default PR base (#167)

Three personalized-fork PRs (#155, #162, #165) were filed against
upstream by accident in one week - GitHub points new fork PRs at the
upstream repo by default, and nothing warned about it at the moment of
filing. Adds a PR template with the heads-up in the compose box (plus
the review norms the process asks for anyway) and one sentence in
CONTRIBUTING's fork section naming the mechanism.

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
Mads Lorentzen
2026-07-16 22:26:45 +02:00
committed by GitHub
co-authored by Claude Fable 5
parent 848eddbecc
commit dd6d7efea6
2 changed files with 20 additions and 0 deletions
+15
View File
@@ -0,0 +1,15 @@
<!-- Heads-up before you publish: if you built this in a personalized fork
(your profile data, your market's job portals, another AI runtime),
note that GitHub points new PRs at the UPSTREAM repo by default.
Those adaptations live in forks - see CONTRIBUTING.md - and get
discovered via the pinned "Community forks & adaptations" discussion (#78).
Check the "base repository" dropdown above before you continue. -->
## What changed and why
## Failing case / reproduction (for fixes)
## Verification
<!-- What you ran, per CONTRIBUTING: python3 tools/lint_skills.py,
python3 tools/check_framework_version.py, bun test / bun run typecheck
in touched CLIs, python3 -m unittest discover -s tests -->