lukaszraczylo 0c7c782d86 fix(gh): confirm failing workflows on a new connection ...

GitHub sometimes answers a workflow run listing from a lagging replica. For one workflow the answer held 135 runs and ended three weeks ago, while the current listing held 414 runs. The client reuses one connection, so a stale replica could answer every request of a scan and the dashboard showed a failure that a newer run had already replaced.

A failing workflow is now requested again on a new connection that skips the response cache. The client keeps the union of both answers, so the newest run decides.

2026-10-02 05:24:46 +01:00

..

auth.go

feat: add GitHub repository dashboard with Prometheus metrics

2026-10-02 04:28:52 +01:00

client.go

fix(gh): confirm failing workflows on a new connection

2026-10-02 05:24:46 +01:00

fetch.go

fix(gh): confirm failing workflows on a new connection

2026-10-02 05:24:46 +01:00

gh_test.go

fix(gh): confirm failing workflows on a new connection

2026-10-02 05:24:46 +01:00