Stale contributor "cursoragent" in repository sidebar after history cleanup

[lorenzopazienza]

🏷️ Discussion Type

Bug

Body

Hello,

The Contributors sidebar on https://github.com/lorenzopazienza/alphafold-tpu-benchmark still shows "cursoragent" (Cursor Agent), but this account has no commits in the repository.

What I verified:

• A fresh git clone --mirror (including pull request refs) contains no commit authored, committed, or co-authored by cursoragent@cursor.com. All authors and committers are Ihab El Bani, Lorenzo Pazienza, and GitHub (web merges).
• GET /repos/lorenzopazienza/alphafold-tpu-benchmark/contributors returns only IhabProjects and lorenzopazienza.
• GET /repos/lorenzopazienza/alphafold-tpu-benchmark/commits?author=cursoragent returns an empty list.
• The sidebar still shows cursoragent several days later, including in a logged-out browser window, so it is not a local cache issue.

I opened Support ticket #4781418, but it was automatically closed and I was directed to GitHub Community.

Could a GitHub staff member please invalidate or rebuild the contributor list for this repository?

Similar issue: https://github.com/orgs/community/discussions/201246

Thank you,
Lorenzo Pazienza

[github-actions[bot]]

💬 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. ⭐

[jarnix]

You did the thorough version of the check (mirror clone with PR refs, author queries), which rules out the usual leftovers. What remains is the sidebar's own cache: it counts Co-authored-by trailers as well as authors, and it is not rebuilt on force-push. Two things have been reported to nudge it, an ordinary forward commit on the default branch or switching the default branch to another branch and back; the documented path is a Support ticket asking to remove cached views, per the "Removing sensitive data from a repository" docs, which is the same purge they run for sensitive-data rewrites.