feat: add stale PR indicator

[Saniya30pawar]

Summary

Added a stale PR indicator to PRMetrics so maintainers can quickly identify open pull requests that have been waiting too long for review.

Closes #257

Type of Change

• Bug fix
• New feature
• Documentation update
• Refactor / code cleanup

Changes Made

• Added stale PR calculation based on PR creation date.
• PRs open for more than the selected threshold are counted as stale.
• Added configurable stale thresholds: 7, 14, and 30 days.
• Added an orange stale PR warning tile in the PR Analytics section.
• Added a GitHub search link for the user’s open stale PRs.
• Updated API response to include stale PR count, threshold, and search URL.

How to Test

Steps for the reviewer to verify this works:

1. Run the app locally.
2. Sign in with GitHub.
3. Open the dashboard.
4. Go to the PR Analytics section.
5. Check that the stale PR tile appears.
6. Change the Stale after dropdown between 7, 14, and 30 days.
7. Confirm the stale PR count updates based on the selected threshold.
8. Click the stale PR tile and verify it opens GitHub search for stale open PRs.

Checks

• npm.cmd run type-check
• npm.cmd run lint

[vercel]

Someone is attempting to deploy a commit to the PRIYANSHU DOSHI's projects Team on Vercel.

A member of the Team first needs to authorize it.

[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

[github-actions]

Thanks for your first PR on DevTrack! 🎉

A maintainer will review it within 48 hours. While you wait:

• Make sure CI is passing (type-check + lint)
• Double-check the PR description is filled out and the issue is linked
• Feel free to ask questions in Discussions if you need help

If you find DevTrack useful, a ⭐ star on the repo is always appreciated — it helps the project grow and attract more contributors!

[Priyanshu-byte-coder]

PR is currently conflicting with main. Please rebase onto main and resolve conflicts before this can be reviewed/merged:

git fetch upstream
git rebase upstream/main
# resolve conflicts
git push --force-with-lease

[Priyanshu-byte-coder]

This PR has merge conflicts with current main. Please rebase on main to resolve before re-requesting review.

[Priyanshu-byte-coder]

Merge conflict on src/app/api/metrics/prs/route.ts. Please rebase against main to resolve before this can be merged. The stale PR indicator enhancement looks useful.

[Priyanshu-byte-coder]

This PR has merge conflicts with main. Please rebase on the latest main branch and re-request review. The approach is approved — just needs conflict resolution.

[github-actions]

🎉 Merged! Thanks for contributing to DevTrack.

If the project has been useful to you, a ⭐ star on the repo is the easiest way to support it — it helps DevTrack get discovered by more developers.

Keep an eye on open issues for your next contribution!