Contribution graph showing duplicate commits after history rewrite

[mateeeeeee]

Select Topic Area

Question

Body

I rewrote the git history on one of my repos to remove a commit, then force-pushed to master. The contribution graph is now wrong number of commits. I believe this happened because GitHub logged contributions for each version of the rewritten commits as separate events. Is there a way to recalculate or correct the contribution data for this repository? Waiting doesn't seem to help though

[BryanBradfo]

Hey @mateeeeeee, you're exactly right. Because of how GitHub logs events, those rewritten commits got new IDs and were counted as brand new contributions, but the old ones weren't automatically subtracted when you force-pushed.

Unfortunately, there is no magic button on our end to force a recalculation. Your best bet is to wait about 24 hours to see if GitHub's internal cleanup jobs catch the orphaned commits. If your graph is still wrong after that, you should reach out to GitHub Support at https://support.github.com/. They have the tools to manually rebuild your contribution graph from their side.

The only other "guaranteed" way to clear it up yourself is to completely delete and recreate the repository. But that obviously comes with a lot of messy side effects like losing issues and PRs, so asking Support is definitely the safer route!

[mateeeeeee]

@BryanBradfo Nope, I only have Copilot, Codespaces, Repositories

[BryanBradfo]

@mateeeeeee Since you don't see Contributions > Contributor Graph directly, do you see "Something else" > "Other support" if you scroll down on the first screen?

You should find something like this:

Clicking that gets you to the General support request form. Fill it as above! I'd choose "other bug" for the category

[mateeeeeee]

@BryanBradfo Thanks for your help, but this is really weird, since I don't have that either (and I am logged in to my account by the way):

[BryanBradfo]

@mateeeeeee I see. In that case, just go ahead and click on Repositories > Repositories - Features.

When you fill out the ticket, just tell them you did a history rewrite and a force-push, and now your repository's total commit count is wrong because it's still including the old orphaned commits. Just ask them to clear those orphaned commits so the count is accurate again. The support team will know exactly what to do behind the scenes to fix your numbers!

For the subject line, you can just put something simple like "Incorrect commit count after history rewrite".
For the main description box, you can paste this: "I rewrote my repository's history and force-pushed. The total commit count is now wrong because the old, orphaned commits are still being counted alongside the new ones. Could you please clear these orphaned commits so the repository's commit count is accurate again?"
For the checkboxes asking which feature this is about, just select "Informations" or "Branches".

[mateeeeeee]

@BryanBradfo Thanks, I reported it through Repositories -> Repository Access Issues (since I am also missing Repositories - Features) and it got resolved quickly.

[BryanBradfo]

@mateeeeeee Awesome! I'm really glad the support team got it sorted out for you so quickly. Happy coding! 🚀

[ash-iiiiish]

Here are the steps to resolve this:

1. Make a test commit
   Push a small, trivial change to the default branch (edit README, add a comment). This sometimes triggers GitHub to reevaluate the repository state and refresh the graph .

2. Wait 24-48 hours
   GitHub's contribution indexing runs on background jobs that can take up to 24-48 hours to fully update after force-pushes . If the inflated counts persist beyond that, proceed to the next step.

3. Contact GitHub Support
   Users cannot trigger a reindex themselves. You need GitHub staff to refresh the contribution data . Submit a request at https://support.github.com/contact with:

Your GitHub username

Repository URL

Date of the force-push

Affected date range (where graph shows wrong counts)

Explanation that commits were rewritten via rebase and force-pushed

Confirmation that local git log shows correct history

The support team can manually reindex your contribution graph to clear the cached entries from deleted commits .

[Mr-Asim-Mr]

accept the answer

[HamzaAshfaq95]

Go to Repositories > Repositories - Features and submit a ticket. For the subject, use: "Incorrect commit count after history rewrite"
In the description, write:
"I rewrote my repository's history and force-pushed. The total commit count is incorrect because orphaned commits are still being counted. Please clear them so the count is accurate."
For the feature checkboxes, select "Informations" or "Branches". The support team will handle the rest!