github-readme-stats icon indicating copy to clipboard operation
github-readme-stats copied to clipboard

2 Bugs: Commit number display wrongly & Keywords have conflicts

Open Octopus058 opened this issue 1 year ago • 4 comments

Describe the bug

Let's see 2 pictures first Oct0pu5's GitHub stats Oct0pu5's GitHub stats

You notice what?

The number of commits is wrong, and wierd, I commited in 2024 more than in total?? Also, both numbers are wrong according to my real commit number👇 commit

Second,

There must be some conflicts between the keywords include_all_commits and count_private 👇(I can't I cannot reproduce it, but i'm sure it happened) wrong

Expected behavior

IDK whether others have these bugs, hope it can be fixed soon :)

Screenshots / Live demo link

Have shown above

Additional context

No response

Octopus058 avatar Sep 19 '24 08:09 Octopus058

@anuraghazra can I work on this?

mayanknegi-kun avatar Sep 29 '24 11:09 mayanknegi-kun

@Octopus058 can you please assign me this project?

Kgpianghosh006 avatar Oct 06 '24 04:10 Kgpianghosh006

sorry but actually i cant set the assignment :/

Octopus058 avatar Oct 06 '24 05:10 Octopus058

@anuraghazra can you assign this to me

Goutamchoudhary907 avatar Oct 15 '24 15:10 Goutamchoudhary907

Hello @Octopus058

Thank you for opening an issue.

At the moment the cards showing that you have 257 commits during the last year and 684 commits total. Your GitHub profile shows tat you have 299 total contributions during the last year, so generally the numbers on the card looks correct.

Image

Also note that we do not provide the &count_private=true option. It does not affect the card. In case you want to display private contributions on your card, then you need to deploy own instance using your own GitHub API token.

Regarding the Something went wrong! Could not fetch total commits problem, this happens sometimes when the upstream GitHub API respond with an error for some reason (for example due to high load). There is not much we can do about it besides rendering clear error message. It should be automatically resolved through some time (30 mins approx.).

qwerty541 avatar Oct 04 '25 17:10 qwerty541