Stale contributor still displayed although API and rewritten history show only the current author

[manas-maheshwari]

🏷️ Discussion Type

Bug

Body

Hello GitHub Community,

The repository https://github.com/pgtriage/pgtriage still displays mmaheshwari-apex in its Contributors section after the commit history was corrected. That username is no longer present in the repository's reachable history.

I corrected the Git author information, rewrote the history, and force-pushed the corrected commits more than 24 hours ago. I have verified all reachable branches and tags. Every current commit is attributed to manas-maheshwari, with no author, committer, or Co-authored-by reference to mmaheshwari-apex.

Additional verification:

• Default branch: main
• The filtered commit page for the stale account shows no matching commits: https://github.com/pgtriage/pgtriage/commits/main/?author=mmaheshwari-apex
• The REST contributors endpoint now returns only manas-maheshwari, with 19 contributions: https://api.github.com/repos/pgtriage/pgtriage/contributors?anon=1
• The repository sidebar still displays two contributors.

Could a GitHub staff member please refresh or rebuild the contributor statistics for pgtriage/pgtriage so the repository page reflects the current history and REST API response?

Repository owner: pgtriage
Correct contributor: manas-maheshwari
Stale contributor entry: mmaheshwari-apex
Default branch: main

Thank you.

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