Stale contributor remains in repository sidebar after complete history rewrite

[Ran1sss]

Hello GitHub Community / GitHub staff,

Please help invalidate or remove a stale contributor entry from this public repository:

• Repository: https://github.com/Ran1sss/OMP-IDE
• Repository ID: 1314227804
• Repository owner and correct contributor: @Ran1sss
• Stale, unrelated account shown in the homepage Contributors sidebar: @Ranis
• Current default branch HEAD: 1788240492ecc368ebaada4c4d09e2c5f02a8f90

Background:

The repository history was rewritten to correct an accidentally misconfigured local Git author identity. The old history used an author identity that GitHub associated with the unrelated account @Ranis. The corrected history was force-pushed with --force-with-lease; all current branches and release tags now point only to rewritten commits.

Current authoritative state:

1. The repository has only one branch (main) and no pull requests.
2. Every one of the 38 commits currently reachable from main has both Git author and committer set to Ran1sss and GitHub resolves every commit to @Ran1sss.
3. GET /repos/Ran1sss/OMP-IDE/stats/contributors has already recomputed and returns only @Ran1sss with 38 commits.
4. The public Insights → Contributors graph shows only @Ran1sss — 38 commits.
5. The repository collaborators list contains only @Ran1sss as admin; @Ranis was never invited and has no access.
6. However, the repository homepage Contributors sidebar and GET /repos/Ran1sss/OMP-IDE/contributors still return the old cached result: @Ranis — 37, @Ran1sss — 1.

I waited for cache propagation and retriggered contributor statistics, but the homepage/sidebar cache remains stale while all current commit and statistics data is correct.

Could GitHub staff please invalidate the repository contributors/sidebar cache and remove the stale @Ranis entry so the homepage reflects the current reachable history?

Thank you.

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