7cc3c1276d* docs: say "security fixes only" for v1 and unpin the PR-template links The v1 maintenance policy was stated two different ways across the docs — "security fixes only" in CONTRIBUTORS.md, "bug fixes" in README.md. The #1819 PR triage told 120 contributors that v1 is security-fixes-only, so that is the wording we keep. Also make the PR template's two CONTRIBUTORS.md links relative instead of pinned to blob/main/. `main` is release-only, so those resolved against the last released tree rather than the branch the reader is on. The remaining AGENTS.md occurrences are left alone deliberately: PR #1866 rewrites those exact lines and lands first. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01YAt8rqxysNbhYWLhoRm3fU * docs: drop the README change; #1866 owns that line The "Repo status" callout edit here patched `(bug fixes only)` → `(security fixes only)` on the callout as it exists on v2/main. But #1866 replaces that entire callout, because the surrounding sentence is false today: it still says "The `main` branch is the legacy v1 implementation", when `main` now holds the latest released v2. So this edit both collides with #1866 on the same line and, taken on its own, would preserve the false statement while correcting only the parenthetical. #1866 already sets the v1 policy wording to "security fixes only" across AGENTS.md and README (ee020ff2), so nothing is lost by dropping it here. This PR is now exactly its intended half: the two branch-pinned `blob/main/CONTRIBUTORS.md` links in .github/pull_request_template.md, made relative. That file is untouched by #1866, so the two PRs no longer overlap on any line. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01YAt8rqxysNbhYWLhoRm3fU --------- Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
35 lines
1.5 KiB
Markdown
35 lines
1.5 KiB
Markdown
<!--
|
|
⚠️ Before you open this pull request, please read our contribution policy.
|
|
|
|
We accept ISSUES, NOT PULL REQUESTS from external contributors.
|
|
|
|
Design and implementation are done by the maintainers through a
|
|
prompt-driven workflow (see AGENTS.md). External source PRs will not be
|
|
merged — they have to be reverse-engineered to fit our component/theme
|
|
conventions and coverage gates, so it's faster for us to re-derive the
|
|
change from your intent.
|
|
|
|
If you've found a bug or want a feature:
|
|
→ Open an issue instead, labeled for the version you're targeting
|
|
(`v1` for `v1/main`, `v2` for `main`).
|
|
|
|
If you've already built the change locally:
|
|
→ Open an issue and share the PROMPT(S) you used to generate it, not a
|
|
diff. We'll reproduce it through our own workflow.
|
|
|
|
Full policy: ../CONTRIBUTORS.md (relative to this template — the file lives
|
|
at the repository root, on whatever branch you're reading).
|
|
|
|
Maintainers: delete this template body and describe your change normally.
|
|
-->
|
|
|
|
> **Heads up:** this repository accepts **issues, not pull requests** from
|
|
> external contributors. Please read [`CONTRIBUTORS.md`](../CONTRIBUTORS.md)
|
|
> before continuing. If you're an external contributor, open an issue (and
|
|
> share the prompt you used, if you've already built the change) rather than
|
|
> this PR.
|
|
>
|
|
> Want to work on the Inspector with us directly? Come say hello in
|
|
> **`#inspector-dev`** on the
|
|
> [MCP Contributor Discord](https://discord.gg/6CSzBmMkjX) — we're happy to
|
|
> scope work with you.
|