Skip to content

docs: add issue templates for the issues-only contribution model #1844

Description

@cliffhall

Split out of #1820 (phase 6), which is otherwise complete.

Why this matters more now than it used to

External pull requests are off — the repo moved to Collaborators-only in phase 6, and CONTRIBUTORS.md documents the issues-only policy. So issues are now the single intake channel for everyone outside the org.

GitHub gives a would-be contributor no explanation when the "Create pull request" button is missing. CONTRIBUTORS.md covers that, but only if they find it. Templates put the policy in front of them at the exact moment they are trying to contribute.

There are currently no templates at all — .github/ISSUE_TEMPLATE/ does not exist.

Suggested set

Template Purpose
Bug report Which client (web / cli / tui), Inspector version, Node version, MCP server + transport, repro steps. Most bug reports currently arrive missing the client and transport, which are the two facts that determine where to look.
Feature request Problem before solution; note that maintainers implement, so a clear problem statement is more useful than a patch.
v1 security issue Should redirect to the advisory process, not collect details in public. See SECURITY.md (restored in #1843).

Plus config.yml with:

  • blank_issues_enabled: false — so everything lands in a template
  • Contact links to CONTRIBUTORS.md (why no PRs), SECURITY.md (private reporting), and the docs site

Worth deciding while writing these

  • Should the bug template ask v1 vs v2? v1 is deprecated and takes security fixes only, so a v1 bug report needs a different answer than a v2 one. Cheapest way to route that is a required dropdown.
  • The MCP spec vs the Inspector. A recurring class of issue is actually about the protocol or the SDK, not this tool. A contact link to the spec repo would deflect some of it before it becomes triage work.

Related

Activity

  1. self-assigned this
    on Jul 28, 2026
  2. added this to the v2.1.0 milestone on Jul 28, 2026
  3. removed their assignment
    on Jul 29, 2026
  4. cliffhall commented on Aug 1, 2026

    @cliffhall
    MemberAuthor

    Triage: Priority = Medium

    Scored 8/16 with the priority rubric added to AGENTS.md in #1891. This card is already approved and sitting in Todo — only Priority was set here, its Status is unchanged.

    Axis Score Reasoning
    Severity / impact 3/5 Issues are now the single intake channel for everyone outside the org, and GitHub gives a would-be contributor no explanation when the PR button is missing. Every issue arriving without repro or version information costs maintainer time on the way back.
    Urgency / staleness 4/5 v2.1.0 milestone, plus specific timing: the #1872 sweep just closed 135 issues telling their reporters to open fresh v2 issues, so an intake spike is arriving into a tracker with no templates.
    Signal bonuses +1 milestone (v2.1.0) (+1)
    Total 8 Lands in the Medium band (6-8).

    Related issues. One connected issue:

    Worth a second look. The timing argument is stronger than the score conveys. If anything in the Medium band should jump the queue, this is the candidate — it gets cheaper the sooner it lands and more expensive with every untemplated issue filed.

    Scores are a starting point, not a verdict — the rubric is meant to be overruled when it's plainly wrong, provided the reason is written down.

  5. self-assigned this
    on Aug 1, 2026
  6. cliffhall commented on Aug 2, 2026

    @cliffhall
    MemberAuthor

    Closed by #1894, squash-merged into v2/main. (Auto-close doesn't fire here — Closes #N only closes on PRs targeting the default branch, and v2 PRs target v2/main.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

v2Issues and PRs for v2

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions