mirror of
https://github.com/Matysh/houseplan-card
synced 2026-09-29 03:09:36 +00:00
Matysh
6ecbedfb85
Validate / changes (push) Successful in 52s
Validate / process-gate (push) Failing after 1m17s
Validate / provenance (push) Successful in 1m20s
Validate / hacs (push) Failing after 16s
Validate / hassfest (push) Failing after 13s
Validate / frontend (push) Successful in 7m30s
Validate / backend (push) Failing after 8m41s
Validate / performance_smoke (push) Failing after 9m45s
Validate / golden (push) Failing after 14m25s
Validate / smoke (push) Failing after 28m53s
Every push to every branch ran 128 browser smokes, 50 golden scenes, a Home Assistant install and a performance pass — including a push that added one spec file. The pipeline made such pushes routine: every spec revision and every review document is a push to a task branch and used to cost the full suite. A changes job classifies the push range; frontend, smoke, golden, performance and backend now run only when their paths moved, and hacs and hassfest only for manifests, translations or Python. provenance and process-gate always run — they judge commits, not code. The exception carries the design. On dev everything runs, always, unfiltered: the beta gate accepts "green Validate at the exact SHA", and if the volume of a run depends on the diff, green stops meaning one thing — a release candidate touches manifests and changelogs, would skip the browser suites under filtering, and a run with skipped jobs still concludes success. That would be the sixth silent success of the week. Filters save time on task branches, where Validate is an early signal and the real acceptance is the code review running gates itself. A new branch with a zero before-sha is classified from the merge-base with dev, not from the root of history. Issue: #136 User-Visible: no