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

Offer the Enry and go-git patches upstream

Aperta
  • Qualcosa non va?
#133 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à
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
25/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
go, ruby
Ambito
devtools, tooling

Direzione di ricerca

Start with third_party/README.md, the two patch files, and their PROVENANCE.json records. Review the named go-git regression and *_close_regression_test.go tests, then inspect update_go_git.py and update_enry.py before coordinating upstream issues and PRs. Done means links are recorded, patch sizes are tracked, and the parity atlas remains exact after regeneration.

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

Descrizione

follow-up

Why

#96 asked for two things: make go install work, and offer dircue's Enry and go-git patches upstream. 1.0.0 delivers the first by embedding the maintained snapshots in the module with recorded provenance. The second is still open: upstream users don't benefit from the fixes, and dircue carries the maintenance alone.

Proposal

go-git. Split third_party/patches/go-git-reader-delta.patch into two PRs:

  1. Streaming delta reconstruction (go-git #2378). The reader could rebuild incorrect bytes after a backward copy followed by a forward copy, with no error. Include the regression test.
  2. File-handle lifecycle. EncodedObjectSize, commondir discovery, lazy readers and packfile-cache eviction. Include the *_close_regression_test.go tests.

dircue's read metrics and the transport-client removal stay local. Upstream would want the latter as an opt-in build tag, if at all.

Enry. First open an issue proposing a Linguist 9.7.0 refresh. Then offer separable PRs:

  • the data regeneration;
  • the pure-Go Flex tokenizer;
  • the centroid classifier;
  • each heuristic or modeline fix, with its Linguist Ruby reference.

Acceptance

  • Upstream issues and PRs are opened and linked from third_party/README.md.
  • Patch sizes are recorded in each PROVENANCE.json and shrink as upstream merges them.
  • Each upstream release that absorbs a patch is followed by regenerating with update_go_git.py/update_enry.py, and the parity atlas stays exact.

Note

Opening upstream PRs is public posting on third-party projects, and it exposes code from a repository that is currently private. Do it once the maintainer decides on timing.

Lingua principale
Go
Stelle
0
Fork
0
Merge medio
5h 8m
PR unite (30g)
54

Preparare l'ambiente

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 war-and-code/dircue

Tutte le issue di war-and-code/dircue

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.