Contribution graph overcounting commits after force-pushes — request recalculation

[Castrozan]

Select Topic Area

Question

Body

My contribution graph shows 258 commits on January 31, 2026 for the repository Castrozan/.dotfiles, but git log only shows about 100 commits on that date.

The inflated count comes from ghost commits created by force-pushes and rebases. On that day there were multiple git reset, pull --rebase, and merge cycles across two machines, which rewrote history and created new commit SHAs for the same work. The original commits were already counted, and the rewritten replacements were counted again.

Evidence:

• git log on main: 100 commits on Jan 31
• git log --all (all branches): 128 unique commits on Jan 31
• git fsck --unreachable: 94 dangling commits authored on Jan 31
• Total accounted: about 222, but GitHub shows 258

I already tried making the repository private, waiting, then making it public again. The contribution count did not change.

Could you please recalculate the contribution graph for my account (Castrozan), specifically for the repository Castrozan/.dotfiles?

Related discussion: https://github.com/orgs/community/discussions/59921

[reyan36]

1. GitHub's contribution graph, which counts commits according to attribution rules rather than just the history of the current repository, differs from the git log in certain ways.

2. GitHub can give credit for both the original and rewritten commits, which inflates the count. Rebases, resets, and force-pushes also generate new commit SHAs.

3. Tracked by commit author and date, contributions are typically not recalculated when history changes.

Users cannot manually cause a recalculation; only GitHub Support may do so if necessary. This behavior is expected.