Insiders Feedback: PRECISE file patching and multiple toolsets in the URL

Abierto
  • ¿Algo no está bien?
#3,567 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 2 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
github, go
Área
backend-api-design, tooling

Línea de trabajo

Start by locating the server-side implementations of create_or_update_file and push_files, then trace how remote-connector URLs parse toolset and header options. The issue does not identify files or tests, so scope the patch format, blob-SHA conflict handling, and URL syntax before implementation. Done means a requested exact or unified diff applies safely against the specified blob and conflicting changes are rejected, while the URL can select a bounded set of toolsets.

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

Descripción

Version: Insiders

Feature: PATCHES ; CUSTOM HEADERS

Feedback:

Two things from daily use through a remote connector:

  1. Precise patching Right now changing one line means pushing the whole file back through create_or_update_file / push_files. For a 200KB doc that's a lot of tokens to add a comma, and a long rewrite through a model is an easy way to corrupt the file. Try add one line to ~MB .ts file. A patch tool would fix it: either old/new string replacement (must match exactly once) or a unified diff, applied server-side against a given blob SHA, rejected on conflict.

  2. Toolset selection in the remote URL The default toolset is too weak, and x/all is too big xd
    every tool schema eats context on each request. I'd like to pick a few toolsets in the URL itself (e.g repos + pull_requests + actions), remote connector config can't set custom headers.

Win & Win situation: a one-line edit to a large file costs roughly the size of the diff, and one connector URL exposes selection of tools instead of all of them.
LESS BANDWIDTH MORE EFFICIENCY

Lenguaje dominante
Go
Estrellas
34.2k
Forks
5.3k
Merge medio
5 d 18 h
PR fusionados (30 d)
13

Preparar el entorno

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.