GitHub repository still shows Claude as a contributor after force-pushing rewritten history

[TejasriKanchu]

🏷️ Discussion Type

Question

💬 Feature/Topic Area

Other

Body

Hello GitHub Community,

My repository still shows claude as a contributor on its main page, even after I rewrote the Git history and force-pushed on October 15, 2026.

Repository: https://github.com/TejasriKanchu/employee-management-system

I checked the commits on origin/main. All commits show my name, TejasriKanchu, as the author and committer. I also searched the commit messages for Co-authored-by, Claude, and anthropic, but found no matches.

The Insights → Contributors graph shows only my account, but the repository's main page still lists Claude as a contributor.

Has anyone experienced this discrepancy? Is there a way to refresh the contributor list safely without rewriting the Git history again?

Thank you!

[mdashifraza7786]

Hi, this can happen because GitHub may cache contributor information separately from the Insights → Contributors graph.

I would first verify the author and committer emails in the current default branch and check for any Co-authored-by trailers. If the Insights graph is already correct, waiting for GitHub's cached contributor list to refresh may be safer than rewriting the history again.

Has anyone confirmed how long GitHub typically takes to refresh this contributor data?

[sukanyamohanty143]

Hi @TejasriKanchu, this may be a GitHub contributor cache issue. Since origin/main contains only your author and committer details, and Insights → Contributors shows only your account, GitHub may not have refreshed the contributor information displayed on the repository's main page yet.

I would recommend:

1. Verify that all branches and tags no longer reference the old commits.
2. Check the commit details for any remaining references to Claude's GitHub account.
3. Wait for GitHub to refresh its cached contributor data.
4. If the discrepancy persists, contact GitHub Support with the repository URL and screenshots of the Contributors graph and repository page.

Since the Insights graph already shows only your account, I would avoid rewriting the Git history again. Another force-push is unlikely to help if the remaining discrepancy is only in GitHub's displayed contributor information.

[RudraBhungaliya]

Discussion Type

Question

💬 Feature/Topic Area

Other

Body

Hello GitHub Community,

My repository still shows claude as a contributor on its main page, even after I rewrote the Git history and force-pushed on October 15, 2026.

Repository: https://github.com/TejasriKanchu/employee-management-system

I checked the commits on origin/main. All commits show my name, TejasriKanchu, as the author and committer. I also searched the commit messages for Co-authored-by, Claude, and anthropic, but found no matches.

The Insights → Contributors graph shows only my account, but the repository's main page still lists Claude as a contributor.

Has anyone experienced this discrepancy? Is there a way to refresh the contributor list safely without rewriting the Git history again?

Thank you!

Here is a direct answer tailored for that GitHub Discussion:

This is a known indexing latency issue with GitHub's repository metadata cache.

When you rewrite Git history using tools like git filter-repo or BFG Repo-Cleaner and force-push (git push --force), GitHub updates the repository tree immediately, but the Contributors list on the repository sidebar is cached separately and relies on background queue processing to update.

Here is why this occurs and how to safely force GitHub to refresh the sidebar:

1. Why Insights → Contributors differs from the main page sidebar
   Insights → Contributors generates its data on-demand from the current commit graph of the default branch (which correctly reflects your rewritten history with only TejasriKanchu).

Sidebar Contributors Widget uses a cached background counter that tracks all commit author emails ever pushed to the default branch—including orphaned/dangling commits that haven't been garbage collected yet by GitHub's servers.

2. How to force GitHub to refresh the Contributor sidebar
   You do not need to rewrite your Git history again. Try these non-destructive steps to trigger a cache refresh:

Trigger an Empty Commit: Push a dummy commit directly to your default branch to force GitHub's cache parser to re-index the repository metadata:

Bash
git commit --allow-empty -m "chore: trigger contributor list cache refresh"
git push origin main
Toggle Default Branch: Temporarily switch your repository's default branch in Settings → Branches to another branch (or create a temporary dev branch), wait a few minutes, and then switch it back to main. This rebuilds the default branch indexing queue.

Wait for GitHub's Garbage Collection: If the dummy commit doesn't clear it immediately, GitHub's internal backend garbage collection usually purges orphaned commit references within 24–48 hours.

If this response helps resolve the indexing discrepancy, please mark it as the accepted answer!

[RudraBhungaliya]

Here is a direct answer tailored for that GitHub Discussion:

This is a known indexing latency issue with GitHub's repository metadata cache.

When you rewrite Git history using tools like git filter-repo or BFG Repo-Cleaner and force-push (git push --force), GitHub updates the repository tree immediately, but the Contributors list on the repository sidebar is cached separately and relies on background queue processing to update.

Here is why this occurs and how to safely force GitHub to refresh the sidebar:

1. Why Insights → Contributors differs from the main page sidebar
   Insights → Contributors generates its data on-demand from the current commit graph of the default branch (which correctly reflects your rewritten history with only TejasriKanchu).

Sidebar Contributors Widget uses a cached background counter that tracks all commit author emails ever pushed to the default branch—including orphaned/dangling commits that haven't been garbage collected yet by GitHub's servers.

2. How to force GitHub to refresh the Contributor sidebar
   You do not need to rewrite your Git history again. Try these non-destructive steps to trigger a cache refresh:

Trigger an Empty Commit: Push a dummy commit directly to your default branch to force GitHub's cache parser to re-index the repository metadata:

Bash
git commit --allow-empty -m "chore: trigger contributor list cache refresh"
git push origin main
Toggle Default Branch: Temporarily switch your repository's default branch in Settings → Branches to another branch (or create a temporary dev branch), wait a few minutes, and then switch it back to main. This rebuilds the default branch indexing queue.

Wait for GitHub's Garbage Collection: If the dummy commit doesn't clear it immediately, GitHub's internal backend garbage collection usually purges orphaned commit references within 24–48 hours.

If this response helps resolve the indexing discrepancy, please mark it as the accepted answer!

[Zahid9985]

Hi @TejasriKanchu,

This is most likely one of two things: a leftover trailer your search missed, or a stale cache.

1. Check for a case-sensitive trailer mismatch

git log --grep is case-sensitive by default. Claude Code adds a trailer like Co-Authored-By: Claude noreply@anthropic.com (capital A and B), so a search for Co-authored-by can miss it. Search case-insensitively and by email too:
git fetch origin
git log origin/main -i --grep="co-authored-by"
git log origin/main --format='%H%n%B' | grep -i -E "claude|anthropic"
git log origin/main --format='%an <%ae>%n%cn <%ce>' | sort -u

GitHub counts Co-authored-by trailers, matched by email, as contributions to the repo’s contributor list. A single remaining trailer on any commit in the default branch history is enough to keep Claude listed.

2. Check whether it’s a stale cache

The Contributors list in the repo sidebar is computed in the background and cached. It doesn’t always refresh right after a force-push. The Insights → Contributors graph uses a different calculation, which explains why the two disagree. To see what GitHub actually has:
gh api repos/TejasriKanchu/employee-management-system/contributors --jq '.[].login'

If claude still appears in the API output, run the case-insensitive search above. Some commit still references it.
If the API shows only your account, the sidebar is stale.

Refreshing it without rewriting history

Push a normal new commit to main (even a small README edit). This often triggers a recalculation.
Wait up to 24 hours, since the cache can take a while to expire.
If it still persists with a clean API result, contact GitHub Support and ask them to refresh the contributor cache for the repository.

Old commits can also remain reachable by SHA, or through pull request refs, until GitHub garbage-collects them. They don’t affect the default-branch contributor list, but Support can purge them if needed.

Hope this helps! If it does, please mark it as the answer.

[Bubblegunn]

One fix that has worked for others: rename the default branch away and back, not the repository. In #210296, @JoshPola96 reports that it cleared a stale contributor from the sidebar, with credit to #197389:

gh api -X POST repos/OWNER/REPO/branches/main/rename -f new_name=main-reindex
# wait about a minute
gh api -X POST repos/OWNER/REPO/branches/main-reindex/rename -f new_name=main

If the repository has pull requests, check refs/pull/* too: they are read-only, so old commits stay reachable there after a force-push (see #211219).

To check what the branch itself still credits: I maintain surviving-lines, and npx surviving-lines --ai-breakdown counts the surviving lines and commits whose trailers name an AI assistant (Co-authored-by: Claude …, Assisted-by:). It counts trailers only, not GitHub's cache.