Expose issue/PR timeline events (incl. `review_requested` timestamps)

Abierto
#3,301 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
68/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
go
Área
api, tooling

Línea de trabajo

Start by reading the existing pull_request_read and issue_read tool entry points and how they call GitHub's Timeline endpoint. Implement a read-only timeline capability with pagination, optional event filtering, and the requested event fields; done means callers can identify review request and re-request timestamps.

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

Descripción

enhancement request ai review
Describe the feature or problem you'd like to solve

There's currently no tool in the GitHub MCP server to read an issue's or pull request's timeline events. That means an agent can't tell when a review was requested (or re-requested) on a PR.

The data exists: GitHub shows it in the PR UI, and the REST API returns it via the Timeline endpoint (GET /repos/{owner}/{repo}/issues/{issue_number}/timeline) as review_requested / review_request_removed events with created_at, requested_reviewer and review_requester. None of the current tools expose it.

We hit this building a review-tracking agent in our project management system, which talks to GitHub only through this MCP server. The agent has to figure out which PRs are waiting on a re-review, meaning the author re-requested review after the reviewer's last review. Without the request timestamp it can't reliably tell a re-review apart from a stale PR.

Proposed solution

Add a read-only tool, e.g. list_issue_timeline_events (or get_pull_request_timeline), that wraps the Timeline endpoint:

  • Inputs: owner, repo, issue_number / pullNumber, optional event_types filter (e.g. ["review_requested", "review_request_removed"]), plus standard pagination
  • Output: event type, created_at, actor, and event-specific fields (requested_reviewer / requested_team, review_requester)

Another option is to add a timeline method to the existing pull_request_read / issue_read tools.

Benefit: agents can reason about when things happened on a PR/issue, not just its current state. Review SLAs, re-review detection and reviewer workload reporting all depend on this. It's read-only, so it fits the existing permission model.

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

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.