[BUG] DashboardHeader sync button gives no user feedback when GitHub API is rate-limited

[Priyanshu-byte-coder]

Summary

When the GitHub API returns 403 (rate limited), the sync button in DashboardHeader spins briefly then stops — no error message shown. User doesn't know why their metrics didn't update.

Steps to Reproduce

1. Exhaust GitHub API rate limit (or mock a 403 response)
2. Click the sync button in DashboardHeader
3. Button stops spinning — no error message appears

Expected Behaviour

Show a toast or inline error: 'GitHub API rate limit reached. Resets at HH:MM. Try again later.' Extract reset time from X-RateLimit-Reset response header.

Implementation Notes

• Parse X-RateLimit-Reset header from failed response
• Convert Unix timestamp to local time string
• Show error in the existing toast/notification system

GSSoC Info

• Difficulty: Intermediate — 35 pts
• Area: Bug Fix / UX

[Archit-arch]

Hey @Priyanshu-byte-coder, Can you assign this issue to me?

[aaryaj154]

Hi @Priyanshu-byte-coder, I’d like to work on this issue.
I’m planning to implement proper 403 rate-limit handling by parsing the X-RateLimit-Reset header and showing a user-friendly toast message with the reset time. Also considering temporarily disabling the sync button during cooldown for better UX.

[mallya-m]

Hi @Priyanshu-byte-coder!
I've already contributed to this repo
(PR #303 merged, #305/#306/#411 under review) and I'd love to tackle
this bug too.

I looked at DashboardHeader.tsx — the sync handler currently swallows
the 403 silently.
My fix:

• Read X-RateLimit-Reset from the response headers on any 403
• Convert the Unix timestamp to local HH:MM using toLocaleTimeString()
• Surface it in the existing toast/notification system already in the
  project — no new dependencies needed
• Disable the sync button until reset time passes to prevent repeated
  failed requests

This is a one-file fix in DashboardHeader.tsx with clean error handling.

Could you also assign this to me?
GitHub: github.com/mallya-m