Profile still shows 169 contributions after history rewrite and force-push

[tgthiag]

🏷️ Discussion Type

Bug

Body

Summary

My profile, @tgthiag, still shows 169 contributions on September 3, 2026 after I rewrote and force-pushed the affected repository histories.

The old September 3 commits are no longer present in the current histories of the affected repositories, but the profile contribution graph has not recalculated.

Evidence

• Profile view: https://github.com/tgthiag?tab=overview&from=2026-09-01&to=2026-09-30
• Most clearly affected repositories:
  • tgthiag/crm_business_it
  • tgthiag/crm_business_it_flutter
• Rechecking the current GitHub commit history for September 3 returns no commits authored by me on that date in those two repositories.
• The screenshot below, captured on September 13, still shows the tooltip “169 contributions on September 3rd.”
• The discrepancy has persisted since at least September 9, when I opened the first support request.

I understand that the graph says “contributions,” not necessarily “commits.” However, this discrepancy appeared after the repository histories were rewritten, and the current histories of the two most obvious repositories no longer match the contribution count shown for that date.

Expected result

The contribution graph should reflect contributions reachable from the current qualifying repository history.

Actual result

The profile graph continues to display 169 contributions for September 3, even though the relevant old commits were removed by the history rewrite and force-push.

Steps already taken

1. Rewrote the affected Git histories.
2. Force-pushed the corrected histories.
3. Verified that the old September 3 commits are no longer present in the current histories of the two repositories above.
4. Waited for GitHub's background statistics/indexing to update.
5. Stopped making further Git changes to avoid creating more rewritten commit objects.

Support requests

I opened two GitHub Support tickets:

• #4741232
• #4753441 — filed specifically under Repositories → Repository Access Issues

Both were closed because my account is limited to self-service support channels such as Community Discussions and GitHub Docs. Neither closure included a technical review of the repositories or a finding that the 169 contributions are correct.

Request

Could a GitHub staff member or moderator please clarify whether this profile contribution data can be reindexed, or escalate this to the team that maintains the contribution graph?

If accounts without direct ticket support cannot request a manual reindex, is there a supported process for clearing stale or orphaned contribution entries after a history rewrite?

I am not asking to restore or modify the repository histories; the current Git history is correct. I only need the profile contribution index to be recalculated.

Related reports

• https://github.com/orgs/community/discussions/189036
• https://github.com/orgs/community/discussions/206614
• https://github.com/orgs/community/discussions/205568

Screenshot

[TongyiDai]

There is one useful new signal in the authenticated GraphQL result: GitHub currently reports 168, not 169, contributions on September 3. The collection also reports hasAnyRestrictedContributions: true and classifies all 220 contributions in the September 3–4 range as restricted; the public per-repository commit contribution list is empty.

That means the graph has changed at least once, but the remaining count cannot be attributed from public repository history alone. It may include private-repository contributions or stale restricted contribution records. GitHub intentionally hides the repository and activity breakdown for restricted contributions, so the two public repositories are not sufficient to prove what all 168 cells represent.

Before requesting a reindex, temporarily enable Activity overview and, if acceptable, Private contributions on your profile, then inspect the September 3 breakdown while signed in. This will not reveal private details publicly; private contributions are shown only as aggregate counts. If it still shows 168 after you verify there were no qualifying private actions that day, update this report with the GraphQL fields restrictedContributionsCount: 220 and contributionCount: 168.

Do not rewrite the repositories again. The remaining mismatch is now in GitHub's private/restricted contribution index, which only GitHub can inspect or rebuild.