ceos/fastmcp
1
0
Fork 0
mirror of https://github.com/PrefectHQ/fastmcp.git synced 2026-08-09 07:09:11 +02:00
Code Issues Projects Releases Packages Wiki Activity

Tune too-long triage heuristic (#3610)

Browse source
This commit is contained in:
Jeremiah Lowin 2026-03-24 14:17:39 -04:00 • committed by GitHub
commit 6f4df1eac4
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 1 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

2
.github/workflows/marvin-label-triage.yml vendored
View file

@ -97,7 +97,7 @@ jobs:
STATUS (apply if applicable):
- needs more info: Issue lacks reproduction steps, error messages, or clear description
- invalid: Spam, completely off-topic, or nonsensical (often LLM-generated)
- too-long: Issue/PR goes beyond what the contributor guidelines ask for. The guidelines ask for a short problem description and an MRE — anything beyond that needs scrutiny. However, DO NOT apply this label if the extra content is a brief, specific root-cause analysis (1-3 sentences) that names concrete functions, files, or code paths in the codebase. That kind of analysis saves triage time and should be welcomed. DO apply this label when the extra content is: proposed code changes or patches, multi-step diagnostic writeups, speculative analysis that doesn't reference specific code, structured reports with multiple headed sections that read like LLM output, or verbose "Fix" sections. The key question: does the extra content demonstrate that the reporter actually read the relevant source code, or does it read like speculation? Short and specific = fine. Long and generic = too much. When applying, do not apply other triage labels. The author needs to condense before triage is worthwhile.
- too-long: Apply when an issue or PR doesn't conform to CONTRIBUTING.md. Issues should be a short problem description, an MRE, and expected vs. actual behavior. PRs should have a focused description of the change — not a report. We don't need summaries of what tests cover, explanations of code we can read ourselves, or speculative root-cause analysis. Common LLM failure modes to watch for: verbose "diagnostic" writeups, large proposed patches in issue bodies, multi-section reports restating what's visible in the diff, and generic analysis that doesn't reference specific code. But these are heuristics, not rules — a complex PR may legitimately need more context, and a brief submission can still be low-quality. Judge by whether the content helps a reviewer or just adds noise. When applying, do not apply other triage labels. The author needs to condense before triage is worthwhile.
WHEN APPLYING too-long: After labeling, post a brief comment using mcp__github__add_issue_comment:
"Thanks for the report. This issue goes beyond what our contributor guidelines ask for — we just need a short problem description and an MRE. Please see our [contributing guidelines](https://github.com/PrefectHQ/fastmcp/blob/main/CONTRIBUTING.md) and condense this issue. We'll triage it once it's trimmed down."