[Fix] Show retry when recent pull requests fail - #3091
Merged
Merged
Conversation
roomote-roomote
Bot
requested review from
brunobergher,
daniel-lxs and
mrubens
as code owners
September 22, 2026 05:32
Contributor
daniel-lxs
approved these changes
Sep 22, 2026
daniel-lxs
left a comment
daniel-lxs
left a comment
Member
There was a problem hiding this comment.
Verified initial-load failure and retry recovery to populated and empty results on the exact head. Cached rows remain usable through a failed background refresh, and filters and unsent Home input are preserved. Desktop/mobile inspection, six focused tests, web typecheck, scoped lint, and formatting passed.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Home's Recent PRs panel now distinguishes an initial load failure from a successful empty result. It uses the shared retryable load state when no cached data exists, while keeping cached pull requests visible during a failed refetch.
Why this change was made
Previously, a failed Recent PRs request fell through to
No recent pull requests. Yet., making an unavailable list look empty and leaving users without a recovery action.Impact
Users can retry Recent PR loading in place without reloading Home or losing the existing All, Draft, and Ready filters. Authenticated desktop and 390 × 844 mobile proof covered request abort, the explicit failure state, request restoration, Retry, and the genuine successful empty response; no provider-side action was used.
Screenshots