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

Aperta
#3,301 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
68/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
go
Ambito
api, tooling

Direzione di ricerca

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.

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

Descrizione

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.

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

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.