The commit count is incorrect!

[lmarosestolato]

Describe the bug

The commit count is incorrect! It is considering 29 commits from this year, 20 of which are from last year.

Expected behavior

The annual count is expected to be correct for each category.

Screenshots / Live demo link

Additional context

No response

[tyleroneil72]

I am experiencing the same problem. Hopefully this is fixed soon.

[andreped]

This seems to have been fixed now. Then again, I am using @rickstaa's variant deployed on vercel. It was 0 yesterday (not just 2024 in total), but today all commits are shown:

[rickstaa]

This seems to have been fixed now. Then again, I am using @rickstaa's variant deployed on vercel. It was 0 yesterday (not just 2024 in total), but today all commits are shown:

Hi @andreped and @lmarosestolato,

@andreped, I think your problems are due to a bug that was present in the codebase in the past (details in Issue #1515). I'm happy to let you know that this issue has been resolved in both my branch and the upstream.

@lmarosestolato, regarding your concerns, there might be some confusion between 'commits' and 'contributions'. This is a typical mix-up, but understanding the distinction is crucial for accurately interpreting the data. I suggest taking a look at this discussion: Number of Commits is Incorrect. It offers a clear explanation and should help clarify any misunderstandings.

[andreped]

@andreped, I think your problems are due to a bug that was present in the codebase in the past (details in Issue #1515). I'm happy to let you know that this issue has been resolved in both my branch and the upstream.

Thank you for the clarification! :]

[Tgentil]

Hi everyone,

I've been following this discussion, and I wanted to share the same issue that I've encountered with my own instance. I have my own fork deployed on Vercel, and it's fully updated ("This branch is not behind the upstream"). However, I'm observing a significant discrepancy in my commit count for 2024.

As of today, January 12, 2024, my commit counter shows a total of 696 commits for 2024. However, when I verify the actual count, it's only 31 commits for this year. This discrepancy is puzzling, and I'm curious if anyone else has experienced something similar with their deployments.

Attached are screenshots of my commit card and the actual number of commits in 2024 for clarity. I hope this helps in diagnosing the issue, and I look forward to any insights or suggestions from the community.

[rickstaa]

Hi everyone,

I've been following this discussion, and I wanted to share the same issue that I've encountered with my own instance. I have my own fork deployed on Vercel, and it's fully updated ("This branch is not behind the upstream"). However, I'm observing a significant discrepancy in my commit count for 2024.

As of today, January 12, 2024, my commit counter shows a total of 696 commits for 2024. However, when I verify the actual count, it's only 31 commits for this year. This discrepancy is puzzling, and I'm curious if anyone else has experienced something similar with their deployments.

Attached are screenshots of my commit card and the actual number of commits in 2024 for clarity. I hope this helps in diagnosing the issue, and I look forward to any insights or suggestions from the community.

Hey @Tgentil. Thanks for the information. Your problem is related to #1053. Please show your support for the bug to be fixed there. When #2107 is finalized and merged, the issue should be resolved.

[lmarosestolato]

@lmarosestolato, regarding your concerns, there might be some confusion between 'commits' and 'contributions'. This is a typical mix-up, but understanding the distinction is crucial for accurately interpreting the data. I suggest taking a look at this discussion: Number of Commits is Incorrect. It offers a clear explanation and should help clarify any misunderstandings.

@rickstaa Regardless of the difference between contributions and commits (which I was glad to learn) there is still a problem. See these prints:

This only contribution that appears there is from this year, more specifically the discussion we are having here, but it is marked as last year's contribution. If you have any doubts, compare with the initial prints, in which there were no contributions.

Now, notice that the majority of contributions are scheduled in February of last year, with only 10 commits scheduled for January of this year, with no other type of 'contribution' beyond them. You can confirm this by going to my profile.
Despite this, 31 commits this year are being counted. So it is not possible to say that it was just a question of interpretation of the terms.

Note: I apologize in advance for any discrepancies in the translation, as English is not my native language.

[rickstaa]

gentil. Thanks for the information. Your problem is related to #1053. Please show your support for the bug to be fixed there. When #2107 is finalized and merged, the issue should be resolved.

Ah, thanks for the explanation 😃. If I understand you correctly then I think #3579 (comment) will also be the answer to your question 🤔.

[lmarosestolato]

@rickstaa I took a look at the issues you pointed out and saw that the solution is in progress. I appreciate the time you dedicated to the solution, even though you were filled to overflowing with things to do. I hope your master's thesis is approved! :)