Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Github Stats card: Total commits count represents last 365 days, not current year as indicated #2501

Closed
harry-graham opened this issue Feb 5, 2023 Discussed in #2498 · 2 comments

Comments

@harry-graham
Copy link

Discussed in #2498.

Overview

On the Github Stats card, the Total Commits (2023) value suggests that it represents the total number of commits made by the user in 2023.

However, the count actually represents the total commits by the user in the last 365 days.

Demonstration of this

Github Stats cards for reference

With count_private: false:

My GitHub stats

[![My GitHub stats](https://github-readme-stats.vercel.app/api?username=harry-graham&hide=stars&show_icons=true)](https://github.com/anuraghazra/github-readme-stats)

With count_private: true:

My GitHub stats

[![My GitHub stats](https://github-readme-stats.vercel.app/api?username=harry-graham&hide=stars&count_private=true&show_icons=true)](https://github.com/anuraghazra/github-readme-stats)

Querying the API

With date range of this year only:

image

With date range of last 365 days, which matches the Github Stats cards shown above (with small difference likely due to caching):

image

@rickstaa
Copy link
Collaborator

rickstaa commented Feb 7, 2023

@harry-graham, thanks for your bug report. This is a known issue and has been discussed at #1053. It is solved when #2107 is merged. Please upvote (i.e. 👍) #1053 and/or #2107 to speed up the merging process (see #1935).

@rickstaa rickstaa closed this as completed Feb 7, 2023
@rickstaa
Copy link
Collaborator

rickstaa commented Feb 7, 2023

@harry-graham, thanks for your bug report. This is a known issue and has been discussed at #1053. It is solved when #2107 is merged. Please upvote (i.e. 👍) #1053 and/or #2107 to speed up the merging process (see #1935).

You can of course already use #2107 on your own fork until it gets merged in the main branch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants