Stale GitHub data persists after failed fetch requests.

[jagriti-aswal]

Problem

Currently, when a GitHub fetch request fails, previously fetched issues/PR data remains visible in the Tracker UI instead of being cleared.

This creates misleading UI behavior because users may think the displayed GitHub data belongs to the latest request even though the current fetch actually failed.

For example:

• Fetch data successfully for one username
• Then perform another fetch using invalid credentials or invalid input
• The new request fails, but old issues/PRs are still displayed

This results in stale GitHub data persisting across failed fetch attempts.

---

Expected Behavior

The application should:

• clear previous issues/PR data before starting a new fetch request
• avoid displaying stale GitHub data after failed fetches
• ensure UI always reflects the latest request state accurately

---

Suggested Improvement

• Reset issues/PR state before initiating a new fetch
• Clear total counts during failed requests
• Improve fetch lifecycle consistency for failed API calls

---

Screenshots

Screenshot 1

Successful GitHub data fetch for a public GitHub account.

Screenshot 2

After entering an invalid/random PAT, the fetch request fails but previously fetched PR data still remains visible in the UI.

Screenshot 3

After refreshing the page, the stale PR data disappears, confirming the displayed data belonged to a previous successful request.

I would like to work on this issue under GSSoC'26. Kindly assign it to me.

[tech-dipesh]

/assign gssoc