Feature Request: Add More Granular Contribution Stats

[pushpakumarbalan]

Hi @jstrieb,

First off, thanks for creating this awesome tool!

It would be great to enhance the github-stats card with more detailed metrics to provide a more holistic view of a user's activity. I believe many users would find this valuable for showcasing their contributions.

Suggested New Stats:

• Total Pull Requests: To show direct code contributions.
• Total Issues Created: To highlight community engagement.
• Total Code Reviews: To demonstrate collaborative efforts.
• Package Downloads: A stat to show the real-world impact of a user's published work.
• Contribution Streak (Current & Longest): A popular metric for showing consistency.

Thank you for considering this enhancement!

[pushpakumarbalan]

Update:

For anyone who comes across this issue — I’ve built my own version of the GitHub Stats card that includes some of the suggested metrics such as Total Pull Requests and Total Issues Created.

You can check it out here:
🔗 https://github.com/pushpakumarbalan/pushpakumarbalan

I’ve also made it available as a template, so feel free to fork or reuse it for your own profile!

(Screenshot for reference) 👇

Hope this helps anyone looking for a similar enhancement!

[RehberOdhano]

Hi @pushpakumarbalan, following up specifically on the Contribution Streak (Current & Longest) item from your list — I looked into how it'd fit into the existing codebase and wanted to share a concrete proposal.

What data is already available

src/statistics.zig:253-339 (getReposByYear) already loops over contributionYears and queries, per year:

contributionsCollection(from: $from, to: $to) {
   totalCommitContributions
   ...
}

It only pulls the yearly aggregate, not day-level detail — so the per-year query loop already exists, it's just missing the calendar sub-field.

Proposal

Extend that same per-year query to also request:

contributionCalendar {
   weeks {
     contributionDays {
       date
       contributionCount
     }
   }
}

Then, combining all years:

• Longest streak — longest run of consecutive days with contributionCount > 0
• Current streak — run of consecutive contributing days ending today (or yesterday, if today has no contributions yet)

Implementation shape:

• Add current_streak / longest_streak fields to the result struct and JSON output
• Add two optional rows to templates/overview.svg
• Gate it behind an opt-in flag (e.g. SHOW_STREAKS env var / CLI arg) so output is unchanged for anyone who doesn't want it

Right now the common workaround (mine included) is pairing this tool with an external, unofficial service (streak-stats.demolab.com) in a second CI step that splices extra rows into the generated SVG and manually resizes it to stay aligned with languages.svg. Native support would remove that dependency for anyone doing the same thing.

@jstrieb — per the README, I know you'd rather discuss before a PR lands. If this (just the streak piece) is something you'd want, happy to put one together — let me know if you'd prefer opt-in vs. always-on, or extra rows vs. a separate card.

[pushpakumarbalan]

@RehberOdhano let me check this