Add committed dashboard-copy parity test (automation vs repoman)

Aperta
  • Qualcosa non va?
#6 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
52/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
github, shell
Ambito
testing-qa

Direzione di ricerca

Start with the existing tests/test-vendor-engine.sh to match the shell test style. The new test should fetch automation's dashboard script and lib files with gh api at a pinned SHA kept as a constant, then diff them against the vendored copies in the automation-health-dashboard skill. Done means the test passes on identical copies, fails when either side changes alone, and has an offline escape hatch. The issue does not settle the cache design or the exact file list.

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

Descrizione

Re-filed from rossoctl/agent-skills#47 (originally opened by @rubambiza) after RepoMan was cloned into this repo. Original discussion/history lives there.

Still applies in repoman: only tests/test-vendor-engine.sh exists; no dashboard-copy parity check. Title updated from "automation vs agent-skills" to "automation vs repoman". Closely related to the standalone-skill resync (#5).

The automation-health-dashboard skill vendors a byte-for-byte copy of the
automation repo's dashboard script + lib set. The RepoMan Phase 5 spec
(§Testing, "Dashboard-copy parity") wants a committed parity assertion so
the copy cannot silently drift — a one-time manual check is exactly how it went
stale before (rossoctl/automation#100, surfaced again by clawgenti on PR #46).

Proposed approach: a committed test that fetches automation's copies via
gh api at a pinned ref/SHA (stored as a constant) and diffs them against the
in-repo copies, failing loudly in CI when either side changes without the
other. Preferred over a vendored snapshot, which is just a second manual copy
that can drift the same way. Costs: a CI network dependency (mitigate with a
short cache or a SKIP_PARITY_CHECK offline escape hatch) and a visible
single-line pinned-SHA bump whenever automation's dashboard changes
intentionally.

Deferred out of PR #46 (verbatim-resync scope); fits the RepoMan Phase 6
dashboard-hardening pass.

Assisted-By: Claude Code

Update: the two inherited github-api.sh correctness bugs that were briefly tracked here have been split out to rossoctl/automation#103 and fixed on the Phase 5 automation branch (re-synced here in f039911). This issue now covers only the committed copy-parity guard (Phase 6).

Lingua principale
Shell
Stelle
7
Fork
1
Merge medio
3g 23h
PR unite (30g)
3

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 rossoctl/repoman

Tutte le issue di rossoctl/repoman

Issue simili

Altre issue su Shell/Bash

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.