Stale contributor still appears on repository page after rewriting Git history #211720

dheerajreddysaddi · 2026-10-31T08:14:46Z

dheerajreddysaddi
Oct 31, 2026

🏷️ Discussion Type

Question

💬 Feature/Topic Area

API

Body

Hello,

I'm trying to resolve a contributor attribution inconsistency in my public repository:

https://github.com/dheerajreddysaddi/insurance-fraud-network-detection

I rewrote the commit author and committer metadata and force-pushed the updated history. It has now been more than 48 hours.

I verified the following:

The current commit history no longer contains srinithya182 as an author or committer.
Insights → Contributors shows only dheerajreddysaddi.
The repository contributors API returns only dheerajreddysaddi.
The repository's main-page Contributors list still displays srinithya182.
The Commits page's user filter also still lists srinithya182.
The discrepancy persists in a private browsing window.

GitHub's suggested solution indicated that contributor data might need refreshing, but my support ticket was closed because only self-service resources are available to my account.

Is there a documented way to refresh or rebuild the main-page contributor display and Commits user filter without rewriting the repository history again?

Thank you.

Dknotten · 2026-10-31T08:36:31Z

Dknotten
Oct 31, 2026

Hey,
GitHub doesnt document a self-service way to refresh or rebuild the mainpage Contributors list or the Commits user filter. Old branches, tags, coauthored-by: trailers, and PRs/forks can all keep the account attached.

My suggestion: Use this to search the whole repo for any traces of the contributor.

git fetch --all --tags
git log --all --format='%H %an <%ae> | %cn <%ce>' | grep -i srinithya
git log --all --format=%B | grep -i 'co-authored-by'

For Authored by
git push origin --delete <branch> delete the branch or rewrite and force push

For Co-authored by
git filter-repo --message-callback remove the trailer from the commit message with the command and then force push

If nothing shows up on the traces its probably a github issue and there isnt much you can do. and i would just advice you to clone the repo and create a new one.

3 replies

dheerajreddysaddi Nov 1, 2026
Author

Update: I completed the additional checks suggested here.

Fetched all pull-request head refs and tags.
Searched the fetched Git history for srinithya182 in author and committer fields; no matches were found.
Searched commit messages for Co-authored-by trailers; no matches were found.
Checked the author-filtered Commits page for srinithya182; it shows no commits.
Insights → Contributors and the Contributors API also show only dheerajreddysaddi.

However, the repository's main-page Contributors list and the Commits page's user filter still display srinithya182.

Could GitHub investigate whether these two UI surfaces have stale contributor attribution or indexing data? Is there a supported way to refresh them without recreating the repository or rewriting its history again?

Dknotten Nov 2, 2026

One more thing to check: Forks share object storage with the parent, so if srinithya182 forked the repo before the rewrite, their fork still holds the old commits. Look at Insights → Forks. If a fork exists, ask them to delete it or sync it to the rewritten history. This is a long shot given your other results, but it’s cheap to rule out.

Other suggestion is to send this message to the support and see what they say

Repository: dheerajreddysaddi/insurance-fraud-network-detection

After rewriting history and force-pushing ( now several days), two UI surfaces still list a user who no longer appears anywhere in the repository’s history: the main-page Contributors list and the Commits page’s user filter, both showing srinithya182

Already verified: no author, committer, or Co-authored-by matches across all branches, tags, and fetched PR refs; the author-filtered Commits page for that user is empty; Insights → Contributors and the Contributors API show only dheerajreddysaddi the behavior persists in a private browsing window.

This appears to be stale contributor data in those two views. Could you re-run the contributor/index refresh for this repository? Id like to avoid recreating the repo or rewriting history again.

dheerajreddysaddi Nov 2, 2026
Author

Thanks for the suggestions. I checked Insights → Forks, and there are no forks of the repository.

I also fetched all branches, tags, and pull-request refs and searched for srinithya182 in commit author and committer metadata, as well as for Co-authored-by trailers. No matches were found. The author-filtered Commits page is empty, and both Insights → Contributors and the Contributors API show only dheerajreddysaddi.

I tried contacting GitHub Support, but my request was closed because my account only has access to self-service resources.

Since the old username still appears in the repository's main-page Contributors list and the Commits page's user filter, is there another way to get this investigated by GitHub staff without recreating the repository?

BugBasherX · 2026-11-01T05:40:48Z

BugBasherX
Nov 1, 2026

Hi @dheerajreddysaddi,

Since Insights → Contributors and the contributors API are already clean, this looks like stale derived data on GitHub's side rather than anything in your history. Those surfaces are served from different caches. There's no documented self-service "rebuild", so I'd do two things: rule out anything on your side that keeps the account attached, then nudge the caches.

1. Check hidden refs and emails, not just usernames

git log --all only covers branches and tags you've fetched. GitHub also keeps refs/pull/*/head for every PR, including ones opened before the rewrite, and you can't delete those yourself. Attribution is also matched by email, so grep for the account's email (including its users.noreply.github.com form), not only the username:

git fetch origin '+refs/pull/*/head:refs/remotes/origin/pr/*' --tags
git log --all --remotes --format='%H %an <%ae> | %cn <%ce>' | grep -i -E 'srinithya182|<their-email>'
git log --all --format=%B | grep -i 'co-authored-by'

2. Separate real history from index staleness

Open this directly:

https://github.com/dheerajreddysaddi/insurance-fraud-network-detection/commits/<default-branch>?author=srinithya182

If it returns zero commits but the user dropdown still lists the account, the history is clean and only the filter's index is stale. That's useful evidence for support.

3. Trigger a fresh recompute without rewriting anything

A normal push to the default branch (even git commit --allow-empty -m "chore: refresh") gives the aggregation a new trigger. This isn't documented and isn't guaranteed, but it's harmless and doesn't touch history.

4. Go back to Support with specifics

If the ticket was closed as self-service, reply with the two surfaces affected, the fact that the API and Insights are correct, and the result of step 2. A server-side cache is something only GitHub can purge.

I'd hold off on recreating the repo. You'd lose stars, watchers, issues, PRs and inbound links, and if the email mapping is what's causing it, the new repo can reproduce the same result.

2 replies

dheerajreddysaddi Nov 1, 2026
Author

Update: I completed the additional checks suggested here.

Fetched all pull-request head refs and tags.
Searched the fetched Git history for srinithya182 in author and committer fields; no matches were found.
Searched commit messages for Co-authored-by trailers; no matches were found.
Checked the author-filtered Commits page for srinithya182; it shows no commits.
Insights → Contributors and the Contributors API also show only dheerajreddysaddi.

However, the repository's main-page Contributors list and the Commits page's user filter still display srinithya182.

Could GitHub investigate whether these two UI surfaces have stale contributor attribution or indexing data? Is there a supported way to refresh them without recreating the repository or rewriting its history again?

BugBasherX Nov 2, 2026

Hi @dheerajreddysaddi,

I found a closely related case that may help: [GitHub Community Discussion #205703](https://github.com/orgs/community/discussions/205703).

In that discussion, the repository owner experienced almost the same problem:

The REST Contributors API showed the correct contributor.
The repository's web interface continued displaying the removed contributor.
GitHub Support did not initially provide a resolution.

However, on August 28, 2026, GitHub staff member @ktravers manually refreshed the contributor list, and the repository owner confirmed that the issue was resolved.

Given that you've already exhausted the repository-side checks, I don't think another history rewrite or repository recreation is warranted.

I'd suggest referencing that resolved discussion and specifically asking @ktravers or another GitHub staff member to investigate your repository.

One additional point: your issue affects not only the homepage Contributors list but also the Commits page author filter. It would be worth asking them to check both rather than assuming that refreshing one will resolve the other.

Unfortunately, I don't know of another guaranteed self-service method to trigger this refresh.

Hopefully, a GitHub Community Manager can help investigate this without requiring you to sacrifice your existing repository.

Barun-Chhetri · 2026-11-01T18:40:53Z

Barun-Chhetri
Nov 1, 2026

Hi,

Based on the checks you've already completed, this appears to be a GitHub-side indexing or caching inconsistency rather than an issue with your repository history.

Since:

The current Git history no longer contains the previous contributor.
Insights → Contributors shows only the correct contributor.
The Contributors API returns the expected result.
The author-filtered Commits page returns no commits for the old contributor.

I would avoid rewriting the history again or recreating the repository. Those actions could cause unnecessary disruption without guaranteeing that the stale UI data will be refreshed.

Unfortunately, GitHub does not appear to provide a documented self-service mechanism to rebuild these contributor indexes.

I would recommend submitting or reopening a GitHub Support request with the repository URL, screenshots, API response, and the affected UI pages. Specifically, ask whether the repository's contributor attribution cache and commit-author filter index can be refreshed server-side.

Hopefully, GitHub can investigate and resolve the inconsistency without requiring another history rewrite.

Thanks for documenting your findings. This could help other developers experiencing the same issue.

1 reply

dheerajreddysaddi Nov 2, 2026
Author

Thank you for the advice. I tried contacting GitHub Support with these details, but my request was closed because my account only has access to self-service resources.

I've verified that the old username does not appear in the fetched Git history, including pull-request refs, and the author-filtered Commits page returns no commits. Insights → Contributors and the Contributors API also show only dheerajreddysaddi. I additionally checked Insights → Forks, and there are no forks.

The stale username remains visible only in the repository's main-page Contributors list and the Commits page's user filter, even in a private browsing window.

Is there an alternative reporting channel or a way for a GitHub staff member to escalate this indexing inconsistency? I'd prefer to preserve the existing repository rather than recreate it.

GitHub Community

Stale contributor still appears on repository page after rewriting Git history #211720

Uh oh!

dheerajreddysaddi Oct 31, 2026

🏷️ Discussion Type

💬 Feature/Topic Area

Body

Replies: 3 comments · 6 replies

Uh oh!

Uh oh!

Dknotten Oct 31, 2026

Uh oh!

dheerajreddysaddi Nov 1, 2026 Author

Uh oh!

Uh oh!

Dknotten Nov 2, 2026

Uh oh!

dheerajreddysaddi Nov 2, 2026 Author

Uh oh!

BugBasherX Nov 1, 2026

Uh oh!

dheerajreddysaddi Nov 1, 2026 Author

Uh oh!

BugBasherX Nov 2, 2026

Uh oh!

Barun-Chhetri Nov 1, 2026

Uh oh!

dheerajreddysaddi Nov 2, 2026 Author

dheerajreddysaddi
Oct 31, 2026

Replies: 3 comments 6 replies

Dknotten
Oct 31, 2026

dheerajreddysaddi Nov 1, 2026
Author

dheerajreddysaddi Nov 2, 2026
Author

BugBasherX
Nov 1, 2026

dheerajreddysaddi Nov 1, 2026
Author

Barun-Chhetri
Nov 1, 2026

dheerajreddysaddi Nov 2, 2026
Author