💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

Why the Sidebar Differs from Insights → Contributors

The discrepancy between the sidebar and the Insights page happens because GitHub calculates them using two different systems:

1. Insights → Contributors: This graph is generated dynamically on-demand by walking the commit DAG of the default branch (main) and mapping commit author emails to verified GitHub accounts.
2. Repository Homepage Sidebar: This is powered by a materialized cache table in GitHub’s database. Routine git push events only append new contributors to this table; when history is rewritten (via git rebase, filter-repo, squashing, or deleting commits), the materialized table does not automatically purge old contributors.

How to Force GitHub to Rebuild the Contributor Cache Yourself

You don't necessarily have to wait for a staff member. You can trigger GitHub's background cache invalidation worker yourself using this proven sequence:

Method 1: The Default Branch Toggle (Most Reliable)

Switching the default branch purges the cached contributor index and forces GitHub's worker to re-scan the commit tree from scratch:

1. Push a temporary branch:

   git checkout -b temp-branch-sync
   git push origin temp-branch-sync

2. On GitHub, go to your repository Settings → General.
3. Under Default branch, click the switch arrows icon (⇄) and switch the default branch to temp-branch-sync.
4. Wait 3–5 minutes while GitHub resets the repository cache.
5. Switch the default branch back to main.
6. Delete the temporary branch:

   git branch -D temp-branch-sync
   git push origin --delete temp-branch-sync

Method 2: Ensure Commits Aren't Reachable from Other Branches or Tags

Even if main only contains your commits, GitHub will retain contributors in the repository metadata if their commits are reachable from other remote branches or tags:

1. Check all remote branches:

   git branch -r

2. Check all tags:

   git tag -l

If any older branches or tags contain the original commits from FB208, yibiaoai, or kkjzio, delete those remote refs.

If the Stale Cache Persists

If the branch toggle does not clear the materialized table within a few minutes, it means a database row lock is holding the record. In that case:

• Open a ticket at support.github.com/contact under Repositories → Contributor graph & statistics.
• Note that your Insights graph already shows 1 contributor (140 commits by liwg1995) and request a manual run of the internal rebuild_contributors job for liwg1995/YuduBid (referencing Contributor graph remains stale after history rewrite #205703).

If the default branch toggle clears the stale contributors from your sidebar, please consider marking this response as the accepted answer!