GitHub MCP doesn't surface metadata indicating GitHub Issue comment is marked as spam

Aperta
#3,321 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
58/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
github, go
Ambito
api

Direzione di ricerca

Start by reproducing the behavior against a GitHub Issue with a comment marked as spam, using the reported GitHub MCP Server environment and version command. Inspect the issue-comment response used by the MCP server; done means the agent can identify the spam status or the comment is excluded, with a regression test covering the behavior.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

bug request ai review
Describe the bug

When a comment in a GitHub Issue is marked as spam, it will be collapsed in the human view, but on the MCP side, the agent has no idea that it's marked as spam. It just treats it like a regular comment.

Affected version

Please run docker run -i --rm ghcr.io/github/github-mcp-server ./github-mcp-server --version and paste the output below

GitHub MCP Server bundled with Copilot SDK 1.0.15-unstable.35393089353.gfc44743, running through runtime 1.0.85-unstable.r35379093703.g3514c9a. Running via Agent Host on VS Code (VS Code version 1.139.0-insider commit 92e4d1b6124d662396f19665be324cbb83eabe83).

Steps to reproduce the behavior
  1. Find a GitHub Issue with a comment in it that is marked as spam
  2. Ask the AI to read the GitHub Issue
  3. It will read the comment that was marked as spam as if it were any other comment. It doesn't know that the comment is marked as spam, even when you directly ask it.
Expected vs actual behavior

I expect the agent to know when a comment is marked as spam. Either that, or not have access to it at all.

Logs

N/A

Lingua principale
Go
Stelle
33.1k
Fork
5k
Merge medio
2g 1h
PR unite (30g)
25

Guida per i contributori

Apri la guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di github/github-mcp-server

Tutte le issue di github/github-mcp-server

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.