GitHub support deadlock: stale Contributors data cannot be resolved through any available channel

[eliv1982]

🏷️ Discussion Type

Bug

Body

Hello GitHub Community,

I am documenting a support-process failure that has left a GitHub-side repository issue unresolved despite following the official guidance.

Repository:
https://github.com/eliv1982/vibe-order-infra

After rewriting repository history and force-pushing the corrected main branch, the obsolete co-author attribution was removed successfully.

The current history reachable from main is clean:

no cursoragent
no cursor.com
no Co-authored-by: Cursor

GitHub Insights → Contributors has already recalculated correctly and shows only my account (eliv1982).

The repository homepage Contributors card, however, still shows cursoragent / Cursor Agent.

This means GitHub is currently showing two conflicting versions of contributor data for the same repository.

The more serious issue is the support path:

GitHub documentation says to wait for contributor data to refresh and contact Support if it remains incorrect.
I waited well beyond 24 hours.
I contacted GitHub Support.
The ticket was automatically closed and redirected me to Community Discussions.
I opened a Community Discussion.
The Community thread was closed and redirected me back to GitHub Support.
I opened additional Support requests, including one explicitly describing this routing loop.
Those requests were also automatically closed.

So the actual escalation path currently looks like this:

Support → Community → Support → automatic closure

There is no repository-owner control to refresh or invalidate the homepage Contributors cache, and rewriting the repository history again would be inappropriate because the repository history and Contributors graph are already correct.

I also found a comparable Community case where the same stale Contributors issue was resolved only after a GitHub staff member manually refreshed the contributor list.

At this point, the problem is not a lack of troubleshooting on the repository side. The available troubleshooting has been exhausted.

The problem is that GitHub is:

displaying stale contributor data on the repository homepage;
providing no self-service mechanism to refresh it;
directing users from Support to Community;
directing them from Community back to Support;
and automatically closing repeated Support requests before staff review.

That is a support deadlock.

I would appreciate a clear answer to one of these two questions:

What is the actual supported escalation path when contributor data remains stale after the documented refresh period and all repository-side data is already correct?
If no self-service path exists, can a GitHub staff member please refresh or invalidate the stale homepage Contributors data for this repository?

I can provide screenshots showing:

the homepage Contributors card still listing cursoragent;
Insights → Contributors showing only eliv1982;
Support redirecting me to Community;
Community redirecting me back to Support;
repeated automatic Support closures.

I am not asking for another generic suggestion to rewrite history, wait another 24 hours, or contact the other support channel. Those steps have already been completed.

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