Contributor List not refreshing

[foothillsfireprevention]

Hello all,

I’ve just replaced our entire repository history with a single anonymized commit by “Alias Foothills,” and force-pushed it over HTTPS:
• Created an orphan branch (clean-main), committed only the final site files under the alias identity
• Force-pushed clean-main to overwrite main
• Removed all old branches and tags containing my previous username

Everything on main now shows exactly one commit by Alias Foothills, but the Contributors graph is still caching the old identities. Could someone please trigger a cache refresh or reindex of the contributors list for this repo?

Thank you!

[Yogeshk76]

Wait 24–72 hours – GitHub's background jobs often reindex on their own.

If it's urgent or hasn't updated after a few days, contact GitHub Support directly:
👉 https://support.github.com/contact
Use the category: Repositories > Graphs and Insights > Contributors Graph.

Include the repo link and clearly mention that:

The full Git history was replaced (via orphan branch + force-push)

Only one anonymized commit remains

The current contributors graph is outdated and needs reindexing.

Hope this helps clarify the situation for others experiencing the same issue.
Feel free to mark this as answered if it resolves your query — happy to help!

[ShubhamGajera]

GitHub’s Contributors graph can take some time (usually up to 24–48 hours) to update after force-pushing or rewriting history, especially when using orphan branches and deleting prior commit history.
Unfortunately, there’s no manual “refresh” button available to force this update. However, here are a few suggestions:
->Wait for the cache to clear naturally — it often refreshes within 1–2 days.
->Make a small dummy commit to main (e.g., editing README), which can sometimes trigger a refresh.
->You can also try removing and re-adding the repository topics or visibility status (e.g., toggle public/private if applicable) to help trigger metadata updates.
If the issue persists beyond 48 hours, you may consider contacting GitHub Support.
Hope this helps!