fix: prevent dashboard username overflow on mobile

[PhanisrideepthiThota]

Summary

Fixed the Dashboard header greeting so a long username can shrink and truncate correctly on narrow/mobile viewports instead of overflowing its container.

Closes #1762

---

Type of Change

• 🐛 Bug fix (non-breaking change that fixes an issue)
• ✨ New feature (non-breaking change that adds functionality)
• 💥 Breaking change (fix or feature that changes existing behavior)
• 📝 Documentation update
• ♻️ Refactor / code cleanup (no functional change)
• ⚡ Performance improvement
• 🔒 Security fix
• 🧪 Tests only

---

What Changed

• Updated src/components/DashboardHeader.tsx.
• Added min-w-0 to the dashboard greeting username text element.
• Preserved the existing truncate behavior so long usernames are truncated instead of overflowing.

---

How to Test

1. Open the Dashboard at a narrow/mobile viewport (around 412px wide).
2. Sign in with an account that has a long display name.
3. Check the greeting in the Dashboard header.

Expected result:

The username should remain within the greeting container and truncate with an ellipsis instead of overflowing the container.

---

Screenshots / Recordings

Before	After
Issue #1762 shows the username overflowing on mobile	Long usernames should truncate within the greeting container

---

Checklist

• Linked the related issue above
• Self-reviewed my own diff
• No unnecessary console.log, debug code, or commented-out blocks
• npm run lint passes locally
• No TypeScript errors (npm run type-check)
• Added or updated tests where applicable
• Updated documentation / comments if behavior changed

---

Accessibility (UI changes only)

• Keyboard navigation works correctly
• Color contrast meets WCAG AA standard
• ARIA labels / roles added where needed
• Tested on mobile / responsive layout

---

Additional Context

The change is intentionally minimal: it only adds min-w-0 to the existing truncated greeting text element. No application logic, state management, API behavior, or component structure was changed.

Local lint/type-check/mobile verification could not be completed because the current local dependency installation is blocked by the existing Node 24/native tree-sitter build environment issue.

[github-actions]

GSSoC Label Checklist 🏷️

@Priyanshu-byte-coder — please apply the appropriate labels before merging:

Difficulty (pick one):

• level:beginner — 20 pts
• level:intermediate — 35 pts
• level:advanced — 55 pts
• level:critical — 80 pts

Quality (optional):

• quality:clean — ×1.2 multiplier
• quality:exceptional — ×1.5 multiplier

Validation (required to score):

• gssoc:approved — counts for points
• gssoc:invalid / gssoc:spam / gssoc:ai-slop — does not score

Type labels (type:*) are auto-detected from files and title. Review and adjust if needed.
Points formula: (difficulty × quality_multiplier) + type_bonus

[deepsource-io]

DeepSource Code Review

We reviewed changes in 6e22da7...16aded6 on this pull request. Below is the summary for the review, and you can see the individual issues we found as inline review comments.

See full review on DeepSource ↗

PR Report Card

Overall Grade

Security   Reliability   Complexity   Hygiene

Code Review Summary

Analyzer	Status	Updated (UTC)	Details
Secrets		Sep 6, 2026 11:38a.m.	Review ↗

---

Important

AI Review is run only on demand for your team. We're only showing results of static analysis review right now. To trigger AI Review, comment @deepsourcebot review on this thread.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[PhanisrideepthiThota]

@Priyanshu-byte-coder The star-required check is failing because the workflow receives a 403 Resource not accessible by integration when calling the GitHub List stargazers API.

My repository star is already active ⭐, so it looks like the workflow itself is affected by the current API access restrictions.

The other CI checks are passing, and the PR code itself is unaffected. Could you please take a look at the star-required workflow when you get a chance? Thanks!

[PhanisrideepthiThota]

@Priyanshu-byte-coder
Just following up on this PR after 4 days. The implementation for #1762 is complete and the main CI checks are passing.

The remaining blocker appears to be the star-required workflow, which is failing with 403 Resource not accessible by integration when the workflow tries to access the stargazers API. My repository star is already active