Stale contributor remains after history rewrite

[lskeda]

🏷️ Discussion Type

Bug

Body

I am the owner of this repository:

https://github.com/lskeda/family-node-kit

The repository homepage incorrectly shows 2 contributors, including isaacmbrown (Isaac Brown).

An early commit was accidentally created with an incorrect Git author identity. I corrected the author, rewrote the history, and force-pushed the corrected main branch.

The current main branch contains only these commits:

72f8cc0 — Add MIT License — lskeda
6e6de28 — Initial public release - Family Node Kit 1.0.0 — lskeda

The current Git history is correct and contains no commits authored by isaacmbrown. However, the repository homepage still displays isaacmbrown in the Contributors section.

I previously contacted GitHub Support about this issue in ticket #4766136. Support closed the ticket and directed me to GitHub Community Discussions.

Could a GitHub staff member please refresh the contributor data for this repository?

I am not looking to rewrite the repository again. The current Git history is already correct.

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

[lskeda]

Update: I have also verified the public GitHub Contributors API for this repository.

The API reports only:

lskeda

while the repository homepage still displays isaacmbrown as a contributor.

This confirms that the current repository history and contributor data are correct, while the homepage contributor display remains stale.

I would appreciate a manual contributor-data refresh if a GitHub Community Manager can perform one.

[kurupdevs]

The Contributors API already returning only you confirms your reachable history is clean — this is the homepage sidebar's separate cache, and waiting won't fix it. There's a self-service way to flush it: switch the default branch away and back.

Since your repo only has main, create a temporary branch first, then:

1. Repo Settings → General → Default branch → switch to the temp branch, Update, confirm.
2. Switch back to main the same way.
3. Delete the temp branch.

Reload the homepage after a few minutes — the contributor list should refresh to match the API. Your history stays untouched; this only busts the cached sidebar.

Do it in a quiet minute: while the default branch is switched, new PRs will default to targeting the temp branch. You need admin on the repo for the switch.