Remove "claude" from contributor list after git filter-repo rewrite

[lasofiko]

🏷️ Discussion Type

Bug

Body

Repository: https://github.com/lasofiko/educational-platform

We used git filter-repo to strip Co-Authored-By: Claude trailers from two commits, then force-pushed all branches. The trailers are gone from
every branch, and gh api repos/lasofiko/educational-platform/contributors correctly returns only the 4 human contributors.

However, the Contributors sidebar on the repo home still shows "claude" as a contributor. It's been over 24 hours since the rewrite.

We believe this is caused by two things:

1. Stale contributor cache — the sidebar hasn't refreshed despite the API being clean.

2. Orphan commits on refs/pull/*/head — the original trailer-bearing commits are still reachable via closed PR refs:

   • 13c247802e13071cb5da41a598e52743685ba36e
   • 5019213caa3628bad2972e1132b5ae77a817003e

   Affected PR refs: Feature Request: Select a column when adding an issue to a project #2, Feature request: support release details #3, iOS bug report: strange backstack behavior when navigating to a file #4, Feature request: support jumping to lines in files #5, #6, #7, Allow For Multiple Answers To Be Marked as Answer #9, More defined voting system #10, Feature Request: Push Notifications and Badges for Requested Reviews #11, Feature Request: Blockquote Button #12, Feature Request: Dual account support/troubles #13.

Could a GitHub staff member please:
a) Garbage-collect the orphan PR refs containing those two commits
b) Trigger a recompute of the repository's contributor cache

My collaborator @Fraimy1 performed the rewrite and can answer technical questions if needed.

Thanks!

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

[v-ember]

Hi @lasofiko ,

If you still need help on this account specific question, I will direct you to our Support page.

This is a public forum, and the community is unable to assist with nor escalate a ticket, but we can assure you it is in the right place. It will be answered in the order it was received based on our team's resources and the amount of tickets ahead of yours.

As no other Community Discussions team members will be able to provide additional help with account related questions I am going to close this discussion. We appreciate your understanding and patience while Support works through your request!