Skip to content

Navigation Menu

Sign in
Appearance settings
community

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly
Appearance settings

@community GitHub Community

Discussion options

quasiblob
Oct 8, 2025

Select Topic Area

Question

Body

Hi

Could you please trigger a recalculation or a cache refresh of my repository's contributor data to resolve this? Or something like that...

This is my repo: https://github.com/quasiblob/ComfyUI-EsesImageCompare
This one shows up: https://github.com/SamiTTL

I accidentally some time ago pushed a change into my public repo with my other account, I removed that change and yet still now I see my other account in repository's main page, on right side contributors list.

My commit history shows only this (the one I'm using right now for this post) account having done total of 4 commits, and I only have a single main branch, so I don't think I missed some commit somehow.

It is super annoying - seems like there is no way for user to hide / update this, or I don't find it.

So the commit history is now correct, but the old account is still incorrectly listed as a contributor on the repository's main page.
You must be logged in to vote

Replies: 1 comment · 2 replies

Comment options

OmSonawane-360
Oct 8, 2025

GitHub’s contributor list on a repository’s main page is generated automatically from the entire commit history, including any commits that were ever pushed — even if those commits were later deleted or reverted. Unfortunately, GitHub doesn’t immediately refresh or recalculate contributor data when history changes.

At the moment, there’s no manual way for users to trigger a contributor cache refresh. The list will typically update automatically over time (after a few days or weeks), once GitHub’s background indexing jobs run again.

If the incorrect contributor is still showing after a long period, you can try:

Making a small new commit (to trigger reindexing).

Or contacting GitHub Support directly via https://support.github.com
and requesting a contributor data refresh for your repository.

In short — your history is correct, but GitHub’s cached contributor data just needs time (or a support request) to catch up.
You must be logged in to vote
2 replies
@quasiblob
Comment options

quasiblob Oct 8, 2025
Author

Thanks, but I wouldn't be here, unless that support page wasn't just a circle that directs me to yet another support page, or to here.

I have no idea if it is even possible to directly contact support, I'm using free Github account for my hobby stuff so it might be that too.

Edit - and I did make a commit, that is when I noticed this thing, it didn't seem to do anything for this - at least not immediately so I guess I'll wait and see what happens.
@OmSonawane-360
Comment options

OmSonawane-360 Oct 8, 2025

How to get support as a free user

  1. Start with the GitHub Support portal
    Instead of going in circles through the help pages, you can begin your request by signing into the support portal directly at https://support.github.com/.
  2. Address account and security issues directly
    For problems like a locked or suspended account, you are able to file a direct ticket through a dedicated form. To make sure your request is handled, be as specific as possible in your subject line and description.
  3. Use the GitHub Community Discussions
    For general questions or feature-related problems, the official GitHub Community is your best option. It is actively monitored by both GitHub staff and other users, and is built to provide support for all users.
    You can access the forums at https://github.com/orgs/community/discussions.
  4. Engage with other GitHub users
    The platform's design focuses on community interaction. You can get help from other users by asking for advice or reporting a bug through one of the following methods:
    Open an Issue in a relevant repository.
    Tag a user by mentioning their username with an @ symbol in a comment on an issue or pull request.
  5. Be patient after a commit
    Regarding your edit, certain changes on GitHub can take time to process. If you made a commit related to the issue, it may take a few minutes for the system to catch up. For example, GitHub Actions sometimes has a delay, and webhooks or other integrations may also have a queue. Waiting to see what happens is a reasonable step.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Repositories The core of version-controlled code storage Question Ask and answer questions about GitHub features and usage
2 participants
@quasiblob @OmSonawane-360
Morty Proxy This is a proxified and sanitized view of the page, visit original site.