mirror of
https://github.com/PrefectHQ/fastmcp.git
synced 2026-08-09 07:09:11 +02:00
93753e137e* Tighten contributor guidelines and too-long triage 🤖 Generated with Claude Code https://claude.ai/code/session_01VTVuVM1t2Mas8F6z8j3wJh * Relax issue length guidance from ~15 lines to "fit in a single screen" 🤖 Generated with Claude Code https://claude.ai/code/session_01VTVuVM1t2Mas8F6z8j3wJh * Fix conflicting no-comment rule for too-long label --------- Co-authored-by: Claude <noreply@anthropic.com>
29 lines
1.7 KiB
YAML
29 lines
1.7 KiB
YAML
name: 💡 Enhancement Request
|
|
description: Suggest an idea or improvement for FastMCP
|
|
labels: [enhancement, pending]
|
|
|
|
body:
|
|
- type: markdown
|
|
attributes:
|
|
value: |
|
|
Thanks for suggesting an improvement to FastMCP!
|
|
|
|
Enhancement issues are the **primary way** features and improvements get into FastMCP. Maintainers use well-written issues to implement changes that fit the codebase's patterns and ship quickly. A clear issue here is more impactful than a PR — see [CONTRIBUTING.md](../../CONTRIBUTING.md) for why.
|
|
|
|
### Before you submit
|
|
|
|
- 🔍 **Check if this has already been requested** — search existing issues first
|
|
- 🎯 **Describe the problem you're trying to solve**, not the solution you want — we'll figure out the best implementation
|
|
- ✂️ **Keep it short.** A motivating description and a concrete use case is the ideal request — aim to fit in a single screen. Skip proposed implementations, API designs, or multi-option analyses — maintainers will figure out the approach. Requests that are difficult to parse will be labeled `too-long` and not triaged until condensed.
|
|
- 🤖 **Using an LLM?** Great — but it must follow these guidelines. Generic LLM output that ignores our contributing conventions will be closed. See [CONTRIBUTING.md](../../CONTRIBUTING.md).
|
|
|
|
- type: textarea
|
|
id: description
|
|
attributes:
|
|
label: Enhancement
|
|
description: |
|
|
What problem or use case does this solve? How does current behavior fall short?
|
|
|
|
Focus on the *what* and *why* — the motivating scenario. You don't need to propose an API or implementation.
|
|
validations:
|
|
required: true
|