`Include_all_commits` sometimes shows incorrect number of commits
See original GitHub issueDescribe the bug
On GitHub Stats the number of commits is currently showing the last years commits, after adding include_all_commits
it decreases as shown below.
Expected behaviour
Shows the number of commits in 2022
Screenshots / Live demo link (paste the github-readme-stats link as markdown image)
Before adding include_all_commits
After adding include_all_commits
Issue Analytics
- State:
- Created 2 years ago
- Reactions:11
- Comments:6
Top Results From Across the Web
'git status' shows incorrect commit count from origin/master
git status will show you the number of commits between your local branch and the remote-tracking one. If you have an unrelated branch...
Read more >git-log Documentation - Git
Skip number commits before starting to show the commit output. ... Sometimes you are only interested in parts of the history, for example...
Read more >Git the gist of it: common commands for a working workflow
I'm a big fan of committing “small and often” because Git is super flexible and updating the history is usually a simple process...
Read more >Sometime git unpushed commit count incorrect
After small time Visual Studio display at bottom status wrong count of unpushed commits (for example, 7 instead 3 real). Refresh button do...
Read more >git-log(1) - FreeBSD
-<number>, -n <number>, --max-count=<number> Limit the number of commits to output. --skip=<number> Skip number commits before starting to show the commit ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I created https://github.com/community/community/discussions/35675 to ask GitHub to make the
totalCommitContributions
andrestrictedContributionsCount
objects available under theuser
object. This feature would allow us to solve #1515 for the Public Vercel instance. Please show your support at https://github.com/community/community/discussions/35675.@Rongronggg9 See #2177 and 4df8094e5266f28f7367552980f4e00b0c9421a9 for a example on how to purge the cache when the GraphQL and Rest api fail.
Further, please read https://github.com/anuraghazra/github-readme-stats/pull/211 because we are currently not fetching commits by year. In short, this is because we are trying to prevent the GraphQL and Vercel timeout limits from reaching. I think we could add this more accurate commit fetching, but it should be disabled by default to prevent any rate limits from being hit on the Public Vercel instance. I"m doing something similar on #2159.