Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Default "build" skip hides tracked first-party source, and explore returns unrelated matches instead of saying so

Aperta
  • Qualcosa non va?
#2,462 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
25/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
csharp
Ambito
search, tooling

Direzione di ricerca

Start with the default skip list that contains build, and with how codegraph_explore reports partial misses, since the #2026 miss diagnostics only cover full misses. Also check how sync handles paths that a changed ignore file un-ignores, and how init/status report skipped directories. The issue offers three separate changes and the maintainer has not chosen one, so agree on scope before writing code. Done means a repro in a .NET repo with a tracked build/ folder either gets indexed or gets a visible warning.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Version: 1.6.2, Windows 11, Claude Code

Our repo (.NET) has a root build/ folder that's real, tracked source: about 86 C# files across several small tool projects (release notes builder, packaging, validators). Their actual build output lives in bin/ and obj/, which are already gitignored. Because build is on the default skip list, none of it was indexed.

That on its own would be easy to spot, but explore didn't tell us anything was missing. A query naming symbols that only exist under build/:

codegraph_explore "ReleaseNotesBuilder Program Main ChangelogParser PersistentData Entry AddFeatures"

returned Main from an unrelated Program.cs elsewhere in the repo plus a C++ Parser class, with no hint that most of the names matched nothing. We only figured it out after querying by file path, which gave "No indexed file uniquely matches". The agent was a few steps into reading the wrong code by then.

Workaround: !/build/ in the root .gitignore, then a full codegraph index. With the negation in .git/info/exclude, codegraph sync reported "Already up to date" and found nothing new; only a full index picked the folder up. include in codegraph.json isn't an option, since the docs say it never resurfaces built-in skipped dirs.

Suggestions:

  1. Don't apply the build skip to a folder that contains tracked project/source files whose output is gitignored, or at least report skipped default dirs with tracked source in init/status, so people know to opt in. #1998 did the first part for JVM packages named build; the same trap exists for .NET and others.
  2. Extend the #2026 miss diagnostics to partial misses: when identifier-like query words match nothing, say so even if other results are returned.
  3. Have sync notice newly un-ignored paths after an ignore-file change, or say that a full index is needed.
Lingua principale
C
Stelle
73.2k
Fork
4.7k
Merge medio
2h 16m
PR unite (30g)
423

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di colbymchenry/codegraph

Tutte le issue di colbymchenry/codegraph

Issue simili

Altre issue su C

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.