rubensworks / renovate-overview / 32131905837

100%

claude/renovate-overview-dashboard-rxltbu: 100%

push

github

Reconcile a refresh against the list instead of replacing it

A refresh used to publish only what the current pass had seen so far. With
more than fifty open pull requests that means the list collapsed to the
first page and grew back as the later pages landed, so rows vanished from
under the cursor.

It also re-read every row's detail and checks, six at a time. A search
result carries no head commit, no mergeability and no checks, so each row
went grey the moment it was re-searched and only got its colour back when
its batch came round -- a minute or more later on a large account.

Now a refresh folds the fresh search results into what is already on
screen. A row GitHub reports as unchanged is returned as the very same
object, so React does not even re-render it; a row that did change keeps
what it was showing and is queued for re-enrichment. Rows the current pass
has not reached yet stay put, and are only removed once every page has
landed and the result set is actually authoritative. Only rows that are new
or changed are enriched.

Background refreshes no longer raise the loading flag either, so the
Refresh button stops flickering to "Refreshing..." on its own.

Since a background refresh no longer re-reads everything, the check
rotation now also revisits settled pull requests every ten minutes, not
just the pending ones every thirty seconds. Rows are marked as polled after
each attempt, so a repository whose checks the token cannot read is retried
on that slow cadence rather than on every tick.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Tpt4TeBwshyk8nbNqyhi8b

978 of 978 branches covered (100.0%)

Branch coverage included in aggregate %.

22 of 22 new or added lines in 1 file covered. (100.0%)

1251 of 1251 relevant lines covered (100.0%)

1104.18 hits per line