Why: GET /api/runs returns at most 200 runs, and the workflow list counts each workflow's runs from that page, so counts and last-run times are wrong once more runs exist.
Done when: the list reads per-workflow run counts and last run from the server (a summary operation or a filter by workflow) instead of counting a page client-side.
**Why**: GET /api/runs returns at most 200 runs, and the workflow list counts each workflow's runs from that page, so counts and last-run times are wrong once more runs exist.
**Done when**: the list reads per-workflow run counts and last run from the server (a summary operation or a filter by workflow) instead of counting a page client-side.
sam
added the buglow labels 2026-11-22 00:20:21 +00:00
Landed in de3bfe296: GET /api/workflow-stats returns each workflow's run count, last run and success rate from the server, and the workflow list reads it instead of counting the 200-run page. task check passed; deployed to staging.
Landed in de3bfe296: GET /api/workflow-stats returns each workflow's run count, last run and success rate from the server, and the workflow list reads it instead of counting the 200-run page. task check passed; deployed to staging.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Why: GET /api/runs returns at most 200 runs, and the workflow list counts each workflow's runs from that page, so counts and last-run times are wrong once more runs exist.
Done when: the list reads per-workflow run counts and last run from the server (a summary operation or a filter by workflow) instead of counting a page client-side.
Landed in
de3bfe296: GET /api/workflow-stats returns each workflow's run count, last run and success rate from the server, and the workflow list reads it instead of counting the 200-run page. task check passed; deployed to staging.