Fix inaccurate commit counts and forked repo stats

[Copilot]

GitHub stats were inaccurate due to: (1) commit counts using all-time data instead of year-specific, (2) forked repos inflating stars/forks/language metrics, and (3) timezone issues in streak calculation.

Year-Specific Commit Count

• Added getYearCommitCount() using GraphQL contributionsCollection API
• Replaced REST /repos/{owner}/{repo}/contributors endpoint which returns all-time counts

// Now fetches year-specific commits via GraphQL
const totalCommits = await getYearCommitCount(username, year, userToken);

Forked Repos Exclusion

• Filtered nonForkedRepos for stats that should reflect user's original work:
  • Stars/forks received
  • Language breakdown
  • Top repos rankings
  • Per-repo commit analysis

Commit Streak Timezone Fix

• Replaced new Date(dateString) parsing with pure arithmetic
• Added parseDateString() returning YYYYMMDD numeric format with validation
• Added areConsecutiveDays() handling month/year boundaries and leap years correctly

Minor

• Fixed case-sensitive username matching in contributor lookup
• Fixed typo: generateComedic Commentary → generateComedicCommentary

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Slightly Innacurate results by the app</issue_title>
<issue_description>The Api results sightly differ from the actual values, especally the forked repos stats, the commit streak etc.</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Slightly Innacurate results by the app #3

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
github-wrapped	Ready	Preview	Comment	Dec 5, 2025 0:32am