Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

Feature Request: Support Codebase Semantic Indexing for Neovim

Ouverte
  • Quelque chose ne va pas ?
#306 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
35/100
Type d'issue
Fonctionnalité
Clarté
Plutôt claire
Activité
Active
Stack technique
neovim
Domaine
developer-experience, tooling

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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!

Langage dominant
Vim Script
Étoiles
11.7k
Forks
821
Aucune PR mergée en 30 j

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de github/copilot.vim

Toutes les issues de github/copilot.vim

Issues similaires

Plus d'issues DevTools

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.