Support standalone inline PR review comments
Los mantenedores suelen responder en 2 días
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Aptitud para principiantes
- 55/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Bien especificado
- Estado de actividad
- Activo
- Stack tecnológico
- github, go
- Área
- api, developer-experience
Línea de trabajo
Start by reading the existing pull request review and comment tool implementations and their tests to see how they handle GitHub API parameters and validation. Then compare that workflow with the REST endpoint described in the issue. Done means a tool can create a standalone inline comment with the listed location parameters, without creating or submitting a review.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Describe the feature or problem you'd like to solve
GitHub's UI allows posting an inline PR comment using "Add single comment", without starting or submitting a pull request review.
With github-mcp-server, the currently supported workflow for inline comments appears to be review-oriented:
- Create a pending review
- Add comments using
add_comment_to_pending_review - Submit the review
This makes sense when an agent is performing a complete code review, but not every inline observation necessarily represents a review.
For example, an agent may simply want to leave a comment such as:
Consider extracting this into a separate method.
on a specific line and continue its workflow.
Currently, doing this requires creating and subsequently submitting a review, which introduces additional state and has different semantics from GitHub's native "Add single comment" functionality.
Proposed solution
Expose a tool for creating a standalone inline pull request review comment, for example:
create_pull_request_review_comment
The tool could map to GitHub's existing REST API:
POST /repos/{owner}/{repo}/pulls/{pull_number}/comments
and accept the corresponding parameters such as:
- repository
- pull request number
- comment body
- commit SHA
- file path
- line / side
- optional start line / start side for multi-line comments
This would allow both workflows:
- Standalone inline comment — equivalent to GitHub's "Add single comment"
- Pending review comments — comments intentionally grouped into a review
Example prompts or workflows (for tools/toolsets only)
An agent inspecting a PR notices one localized issue and wants to comment directly on the relevant line:
This timeout is hard-coded. Should this use the configured request timeout instead?
The desired behavior would be to publish that comment immediately on the relevant line, without creating a pending review or requiring a subsequent review submission.
Additional context
I noticed that github-mcp-server explicitly supports and encourages the pending-review workflow, so the absence of standalone inline comments may be an intentional design decision.
If so, it would be useful to understand whether there is a technical, security, or agent-workflow reason for not exposing GitHub's standalone inline-comment API.
This request is not intended to change or replace add_comment_to_pending_review. It is about exposing the separate GitHub capability for cases where an agent wants to publish an individual inline comment without creating a review.
- Lenguaje dominante
- Go
- Estrellas
- 34.4k
- Forks
- 5.3k
- Merge medio
- 3 d 10 h
- PR fusionados (30 d)
- 11
Preparar el entorno
- Incluye un Dockerfile o un archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de github/github-mcp-server
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
github/github-mcp-server#3865 ·
Los mantenedores suelen responder en 2 días
-
update_issue_labels is annotated destructiveHint: false but replaces (removes) existing labelsPosiblemente ocupada @shhhhhhjokerist la tomó hace 6 días. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 69/100
github/github-mcp-server#3760 · 1 comentario ·
Los mantenedores suelen responder en 2 días
-
docs(install-claude): "environment variable" examples put the PAT in argv and the saved configPosiblemente ocupada @shhhhhhjokerist la tomó hace 6 días. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
github/github-mcp-server#3758 ·
Los mantenedores suelen responder en 2 días
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 69/100
github/github-mcp-server#3729 ·
Los mantenedores suelen responder en 2 días
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
github/github-mcp-server#3722 ·
Los mantenedores suelen responder en 2 días
Todos los issues de github/github-mcp-server
Issues similares
-
kind/features
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
TencentBlueKing/bk-nodemgr#4017 ·
Los mantenedores suelen responder en 1 día
-
ssa: wait errors drop the kstatus message, so health check failures don't say whyPosiblemente ocupada @schdief la tomó hoy. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
equinor/radix-operator#2066 ·
Los mantenedores suelen responder en 2 días
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 67/100
microsoft/terraform-provider-msgraph#188 · 1 reacción ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 77/100
Los mantenedores suelen responder en 2 días