Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

Feature Request: Support Codebase Semantic Indexing for Neovim

Offen
  • Stimmt etwas nicht?
#306 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
35/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
neovim
Bereich
developer-experience, tooling

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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!

Vorherrschende Sprache
Vim Script
Sterne
11.7k
Forks
821
Keine gemergten PRs in 30 T.

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus github/copilot.vim

Alle Issues in github/copilot.vim

Ähnliche Issues

Weitere Issues zu DevTools

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.