Skip to content

Commit e4e721e

Browse files
cliffhallclaude
andcommitted
chore: sync the PR template with v2/main after #4961
Takes .github/pull_request_template.md from v2/main, which reduced it to the issues-not-PRs banner (#4960), so this branch stays byte-identical to v2/main. Co-Authored-By: Claude Opus 5.5 <[email protected]> Signed-off-by: cliffhall <[email protected]>
1 parent 9e62490 commit e4e721e

1 file changed

Lines changed: 0 additions & 80 deletions

File tree

‎.github/pull_request_template.md‎

Lines changed: 0 additions & 80 deletions
Original file line numberDiff line numberDiff line change
@@ -1,86 +1,6 @@
1-
<!--
2-
⚠️ Before you open this pull request, please read our contribution policy.
3-
4-
We accept ISSUES, NOT PULL REQUESTS from anyone but the repository
5-
maintainers, organization members with write access included.
6-
7-
Design and implementation are done by the maintainers through a
8-
prompt-driven workflow (see AGENTS.md). Outside pull requests are closed,
9-
not merged: a diff written outside that workflow has to be reverse-engineered
10-
to fit our conventions, tests and gates, so it's faster for us to re-derive
11-
the change from your intent.
12-
13-
If you've found a bug or want a feature:
14-
→ Open an issue instead, using the Bug report or Feature request form.
15-
16-
If you've already built the change locally:
17-
→ Open an issue and share the PROMPT(S) you used to generate it, not a
18-
diff. We'll reproduce it through our own workflow.
19-
20-
If you want to list or add a server:
21-
→ Publish it to the MCP Server Registry instead
22-
(https://github.com/modelcontextprotocol/registry).
23-
24-
Full policy:
25-
https://github.com/modelcontextprotocol/servers/blob/main/CONTRIBUTING.md
26-
27-
Maintainers: delete this comment and the banner below, keep the first line
28-
as `Closes #<ISSUE_NUMBER>`, and fill in the sections.
29-
-->
30-
311
> **Heads up:** this repository accepts **issues, not pull requests**, from
322
> anyone but the repository maintainers. Please read
333
> [`CONTRIBUTING.md`](https://github.com/modelcontextprotocol/servers/blob/main/CONTRIBUTING.md) before continuing. If you're not a
344
> maintainer, open an issue (and share the prompt you used, if you've already
355
> built the change) rather than this PR. To make a server discoverable, publish
366
> it to the [MCP Server Registry](https://github.com/modelcontextprotocol/registry).
37-
38-
Closes #<ISSUE_NUMBER>
39-
40-
## Description
41-
42-
## Server Details
43-
44-
<!-- If modifying an existing server, provide details -->
45-
46-
- Server: <!-- e.g., filesystem, git -->
47-
- Changes to: <!-- e.g., tools, resources, prompts -->
48-
49-
## Motivation and Context
50-
51-
<!-- Why is this change needed? What problem does it solve? -->
52-
53-
## How Has This Been Tested?
54-
55-
<!-- Have you tested this with an LLM client? Which scenarios were tested? -->
56-
57-
## Breaking Changes
58-
59-
<!-- Will users need to update their MCP client configurations? -->
60-
61-
## Types of changes
62-
63-
<!-- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->
64-
65-
- [ ] Bug fix (non-breaking change which fixes an issue)
66-
- [ ] New feature (non-breaking change which adds functionality)
67-
- [ ] Breaking change (fix or feature that would cause existing functionality to change)
68-
- [ ] Documentation update
69-
70-
## Checklist
71-
72-
<!-- Go over all the following points, and put an `x` in all the boxes that apply. -->
73-
74-
- [ ] I have read the [MCP Protocol Documentation](https://modelcontextprotocol.io)
75-
- [ ] My changes follows MCP security best practices
76-
- [ ] I have updated the server's README accordingly
77-
- [ ] I have added a changeset (`npm run changeset`) if this changes what a TypeScript server publishes
78-
- [ ] I have tested this with an LLM client
79-
- [ ] My code follows the repository's style guidelines
80-
- [ ] New and existing tests pass locally
81-
- [ ] I have added appropriate error handling
82-
- [ ] I have documented all environment variables and configuration options
83-
84-
## Additional context
85-
86-
<!-- Add any other context, implementation notes, or design decisions -->

0 commit comments

Comments
 (0)