Stale cursoragent contributor remains after history rewrite and force-push

[sshiong]

Repository

https://github.com/sshiong/agent-browser-cloud

Problem

I own this public repository. Cursor CLI previously added this trailer to five commits:

Co-authored-by: Cursor <cursoragent@cursor.com>

I rewrote the full reachable history on August 20, 2026 and force-pushed main. More than 24 hours have passed, but the repository homepage still shows Contributors (2) and lists cursoragent.

Verification

• The default branch is main.
• The repository has one branch, one tag, no pull requests, and no forks.
• Every reachable commit is authored and committed only by the repository owner.
• No reachable commit contains cursoragent, @cursor.com, or a Cursor co-author trailer.
• GET /repos/sshiong/agent-browser-cloud/contributors returns only sshiong (224 commits).
• GET /repos/sshiong/agent-browser-cloud/stats/contributors also returns only sshiong.
• The repository homepage still visibly displays cursoragent.

Old unreachable commits

GitHub still returns these old rewritten commits by SHA, even though no branch, tag, pull request, or fork references them:

• d0b04618e39240b767d53651546585c908161f54
• 4b358f80749e5d0b6be24dc668b2befe6825fad9
• 9a5cc9ba7590d05328a2903e3de2d68fe92bbc17
• 8f9c0f122b9d3a3d8e8e0009b34f31788ecc11e6
• e4c1190bd331b61dec98cc8e1fdbfaf97645e960

Could a GitHub staff member please trigger a rebuild or invalidation of the repository homepage contributor cache, or advise the correct route for a GitHub Free repository owner when Support says technical support is not included?

GitHub documentation says contributor data should refresh in about 24 hours after history changes and recommends contacting Support afterward. The current reachable history and both contributor APIs are already correct; only the repository homepage display remains stale.

[github-actions[bot]]

Thank you for your interest in contributing to our community! We currently only accept discussions created through the GitHub UI using our provided discussion templates. Please re-submit your discussion by navigating to the appropriate category and using the template provided.

This discussion has been closed because it was not submitted through the expected format. If you believe this was a mistake, please reach out to the maintainers.