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

CI lint, coverage floor and remaining hygiene gaps

Aperta
  • Qualcosa non va?
#170 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
48/100
Tipo di issue
Refactoring
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
github-actions, go, python, rust
Ambito
build-system, ci-cd, testing

Direzione di ricerca

Start with tests/ci/test_workflow_policy.py, structural-worker.yml, ci.yml:98–103, tests/registries/npm_conformance.py, and prototypes/structural/driver/main_test.go, then review docs/CI.md and RELEASING.md for policy constraints. Done means the specified lint, coverage-floor, arm64, on-demand npm, and prototype-cleanup gaps are addressed while all workflows remain event-driven with no schedule: triggers.

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

Descrizione

enhancement follow-up

CI lint, coverage floor and remaining hygiene gaps

Background

Issue #92 re-structured CI into event-driven tiers. On main, the event-driven policy is enforced and all 11 workflows are schedule:-free. Several hygiene items from the issue's acceptance criteria are missing.

What 1.0 ships

  • All 11 CI workflows are event-driven. tests/ci/test_workflow_policy.py enforces the schedule: prohibition.
  • staticcheck v0.6.0 runs in CI (Linux only).
  • cargo audit runs in structural-worker.yml.
  • SHA-pin check: tests/ci/test_workflow_policy.py::test_external_actions_use_full_commit_hashes passes.
  • Coverage profiles uploaded as CI artifacts; summary printed to $GITHUB_STEP_SUMMARY.

Remaining work (acceptance criteria from #92)

Lint:

  • golangci-lint with a committed .golangci.yml config. The issue specifies golangci-lint; staticcheck was substituted. Add golangci-lint (or document the substitution explicitly in docs/CI.md).
  • cargo clippy -D warnings for the structural worker, in structural-worker.yml.

Dependency automation:

  • Out of scope by policy: RELEASING.md keeps Dependabot/Renovate and scheduled automation off until the maintainer enables them. Dependency and action-pin updates stay manual.

Coverage floor:

  • A CI step that reads the coverage artifact and fails if total coverage drops below the current floor. The current floor is approximately 82.6%; the exact number must be committed.

Test execution gaps:

  • linux-arm64 test execution (currently cross-compiled only; ci.yml:98–103 notes this).
  • npm registry conformance (tests/registries/npm_conformance.py) as an on-demand workflow_dispatch job, since it uses the network and ordinary CI does not.

Prototype cleanup:

  • Remove time.Sleep(time.Minute) from prototypes/structural/driver/main_test.go:20.

All CI additions must remain event-driven. No schedule: triggers.

Links

  • #92 (1.0.0 issue being closed)
  • docs/CI.md
  • tests/ci/test_workflow_policy.py
  • structural-worker.yml
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.