Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

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

Abierto
#3,321 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
58/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
github, go
Área
api

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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

Lenguaje dominante
Go
Estrellas
33.1k
Forks
5k
Merge medio
2 d 1 h
PR fusionados (30 d)
25

Guía de contribución

Abrir la guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de github/github-mcp-server

Todos los issues de github/github-mcp-server

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.