Contributors graph shows a removed GitHub App identity (cursoragent) with no matching commits or authorized history

[gentkrasniqii1]

🏷️ Discussion Type

Bug

Body

The Contributors graph on my repository (gentkrasniqii1/prizren-smart-city) shows "cursoragent" as a contributor (3 commits, +2433/-305), even though:

1. The "Cursor" GitHub App was installed on this repo at one point and has since been fully uninstalled (Settings → GitHub Apps → Configure → Uninstall).
2. Filtering commits by that author returns nothing:
   https://github.com/gentkrasniqii1/prizren-smart-city/commits/main?author=cursoragent
   → "No commits history"
3. A full local search across all branches/refs (git log --all --author="cursor" -i, git fetch origin first to ensure everything is up to date) also returns zero matches.

This looks like the same class of issue reported here, where the contributors graph (powered by the separate stats/contributors aggregation pipeline) becomes inconsistent with the actual commit/author data returned by the ?author= filter and git log:
https://github.com/orgs/community/discussions/199910

In that thread, a community member suggested this can require a manual reindex of the contributors graph on GitHub's side, since the stats pipeline doesn't always reconcile itself with current commit history.

Steps to reproduce

1. Visit: https://github.com/gentkrasniqii1/prizren-smart-city/graphs/contributors
2. See "cursoragent" listed with 3 commits, 2433++/305--
3. Visit: https://github.com/gentkrasniqii1/prizren-smart-city/commits/main?author=cursoragent
4. See "No commits history"

Expected behavior
The Contributors graph should match what ?author= and git log --all show — i.e., cursoragent should not appear since it has no attributable commits in the current history, and the associated GitHub App has already been uninstalled.

Actual behavior
Contributors graph still shows cursoragent with stale commit/line-change stats.

Additional info

• No git history rewrite (rebase/force-push) has been performed — the commits genuinely aren't part of reachable history, so this appears to be a stale/cached stats issue rather than something fixable on my end.
• Could a GitHub staff member confirm whether this repo's contributors graph can be manually reindexed/refreshed?

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

[shotorouu]

This happens because GitHub's contributor graph runs on an asynchronous caching service that doesn't automatically update when an integration is removed.

Quick Ways to Invalidate the Cache

Push an empty commit: Run git commit --allow-empty -m "trigger stats reindex" locally and push it to your main branch. Pushing new activity to the repository forces the background stats pipeline to re-scan reachable commits and rebuild the list.

Hit the API directly: Request the repository's contributor stats using curl: curl -i -H "Accept: application/vnd.github+json" https://api.github.com/repos/gentkrasniqii1/prizren-smart-city/stats/contributors. The first request triggers a background calculation on GitHub's backend, and a follow-up request a few seconds later will pull the freshly calculated data.

If neither of those forces the stale cursoragent entry to drop off, a GitHub staff member will need to manually purge the cached stats for that repository from their end.