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

Feature Request: Support Codebase Semantic Indexing for Neovim

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

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
neovim
Área
developer-experience, tooling

Línea de trabajo

Start by reading the existing copilot.vim LSP infrastructure and checking whether the underlying Copilot service supports repository indexing. Define how a repository index would be built, updated, queried, and supplied to requests, then verify the proposed command and cross-file retrieval against a large repository.

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

Descripción

Feature Request: Support Codebase Semantic Indexing for Neovim

GitHub Copilot in VS Code provides Codebase Semantic Indexing, including the Chat: Build Codebase semantic index command. This is very useful when working with large repositories because Copilot can identify and retrieve relevant files and code across the codebase.

It would be very valuable to have similar functionality available in Neovim through copilot.vim.

Motivation

For a small/local coding task, the current Copilot experience works well. However, for a large codebase, repository-level context becomes increasingly important.

Without semantic codebase indexing, Neovim users may need to manually navigate to relevant files and provide context through multiple interactions. This can make large-codebase tasks less efficient and potentially result in significantly more context/tokens being used.

For example, for a request such as:

"Add a new workflow similar to the existing payment workflow."

Copilot should ideally be able to discover the relevant controllers, services, interfaces, implementations, configuration, and tests across the repository rather than relying primarily on the currently open files.

Proposed feature

Provide a way to build and maintain a semantic index of the current repository, similar to VS Code's:

Chat: Build Codebase semantic index

For example:

:Copilot build-codebase-index

The implementation could ideally reuse existing Copilot/LSP infrastructure if the underlying Copilot service already supports repository indexing.

Useful capabilities would include:

  • Build an index for the current repository
  • Incrementally update the index as files change
  • Search/retrieve relevant code and symbols for Copilot requests
  • Support repository-level and cross-file questions
  • Use retrieved context when generating or modifying code
  • Avoid sending unnecessary repository content to the model
Expected benefit

This would make Copilot in Neovim much more effective for large repositories, especially for:

  • Multi-file feature implementation
  • Refactoring
  • Cross-file code understanding
  • Large-scale code generation
  • Finding relevant implementations and call paths
  • Reducing unnecessary context/token usage

VS Code already provides this capability, so bringing equivalent repository-level semantic indexing to Neovim would significantly improve the large-codebase experience.

Thank you!

Lenguaje dominante
Vim Script
Estrellas
11.7k
Forks
821
Sin PR fusionados en 30 d

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/copilot.vim

Todos los issues de github/copilot.vim

Issues similares

Más issues de DevTools

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.