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

Showing number of commits from last 1 year instead of the current year

Open Showrin opened this issue 3 years ago • 10 comments

Describe the bug The card is showing the number of commits from the last 1 year. Like: Total Commits (2021): 1.5k. As it's saying 2021 in the bracket, then shouldn't it either show the commits (620) from the year 2021 or show Last 1 year instead of 2021?

Expected behavior It should show the commit from the current year or change Total Commits (2021) to Total Commits (Last 1 year).

Screenshots / Live demo link (paste the github-readme-stats link as markdown image) Screenshot 2021-05-11 at 1 22 03 PM

Showrin avatar May 11 '21 07:05 Showrin

Yes, the expected behavior is to show the contributions from last year and I support your opinion that this is misleading https://github.com/anuraghazra/github-readme-stats/pull/211#issue-457030914

florianbussmann avatar May 11 '21 18:05 florianbussmann

As pointed out in #1815 the current behaviour is misleading and should be fixed. As pointed out by @hashfx the card should have an option to choose between year-wise, current year or total. Further, the active mode should be displayed on the card. I am currently very short on time, so I can not implement this myself but feel free to create a PR for this feature to review. I added the label since I think this is an important bug that should be fixed.

rickstaa avatar Jun 14 '22 07:06 rickstaa

Hi is this sovled?

asifurrahaman754 avatar Oct 01 '22 13:10 asifurrahaman754

hey there, I want to work on this. @rickstaa Can you please assist me

adi-uchiha avatar Oct 01 '22 19:10 adi-uchiha

@adi-uchiha This is still an issue. It would be great if this behaviour is improved. 💪🏻 I assigned you to this issue since I already assigned @asifurrahaman754 to several issues. Feel free to contact me if you have any questions.

rickstaa avatar Oct 02 '22 11:10 rickstaa

@adi-uchiha, while checking #2107, I noticed that #1053 and #764 are related and that #1053 should best be solved in #2107 since this PR adds a lot of new code. Merging #1053 will therefore solve this issue. Sorry for the confusion.

rickstaa avatar Oct 16 '22 09:10 rickstaa

This issue is solved when #2107 is merged.

rickstaa avatar Oct 16 '22 09:10 rickstaa

Related to #764.

rickstaa avatar Jun 16 '23 07:06 rickstaa

is this issue solved ? If not can you assest me I am quite interested on working this issue

alihamza1221 avatar Sep 28 '23 13:09 alihamza1221

is this issue solved ? If not can you assest me I am quite interested on working this issue

Hey, @alihamza1221! Thanks for your interest to the our project and considering contributions. Looks like we already have pull request https://github.com/anuraghazra/github-readme-stats/pull/2107 which will resolve this issue. Feel free to choose another issue that you are interested to work on.

qwerty541 avatar Sep 29 '23 15:09 qwerty541