include_all_commits=true shows incorrect amount of commits and Total Commits 2023 is equal to Total Commits

[MitkoVtori]

My Total Commits are 1.9K

If I use include_all_commits=true, they become 1.6K, but when I remove it, it says Total Commits (2023): 1.9k(which is my total commits for all years).

[rickstaa]

@MitkoVtori This is because with the include_all_commits flag it uses the search function of the Rest API, which is known to be inaccurate. You can test this out by using the following syntax in the GraphQL explorer:

query userInfo($login: String!) {
  user(login: $login) {
    name
    login
    contributionsCollection {
      totalCommitContributions
      restrictedContributionsCount
    }
  }
}

{"login": "MitkoVtori"}

and then the check the following REST request:

https://api.github.com/search/commits?q=author:MitkoVtori

Graphql gives: 1881
The REST API gives: 1568

The Rest API is used because fetching all commits through the GraphQL API is too expensive on the public instance and will cause the rate limits to be reached. I created a feature request with GitHub to improve this (see https://github.com/orgs/community/discussions/35675). Please add your support to that feature request if you want to see the situation improved.

We might be able to improve this behaviour by merging #1691 and making that behaviour available under an environmental variable. We can then enable it through this variable under the Vercel instances that are deployed by users or the experimental GRS GitHub action.

[MitkoVtori]

@rickstaa Thank you for the support. I hope GitHub accepts your feature request. Until this happens, I can proceed using the Total Commits (2023), even though they're incorrect because it shows my total :)