Stale Contributors sidebar after default-branch history rewrite

[iamzjt-front-end]

🏷️ Discussion Type

Bug

Body

Repository

https://github.com/iamzjt-front-end/fund-pulse

Problem

The repository homepage still shows 100 contributors from an old, no-longer-reachable history, although the current default branch and GitHub REST API report only the current owner.

Current state

• The main history was replaced on July 10, 2026.
• Current remote main has 102 commits.
• The REST contributors endpoint returns only iamzjt-front-end with 92 contributions:
  https://api.github.com/repos/iamzjt-front-end/fund-pulse/contributors?per_page=100&anon=1
• The current default branch contains no Co-authored-by trailers.
• The legacy contributor accounts are not reachable from the current default branch.

Stale result

The repository homepage's server-rendered Contributors fragment still reports 100 contributors (14 visible entries plus "+86 contributors") and lists legacy accounts such as 1zilc, dependabot[bot], and amilajack:
https://github.com/iamzjt-front-end/fund-pulse/contributors_list?current_repository=fund-pulse&deferred=true

The stale result also appears in fresh unauthenticated requests and has persisted after multiple pushes for 12 days.

This appears to be the same class of cache mismatch discussed in #202538 and #189812, but in this case the stale entries come from a completely replaced repository history.

This is a UI-template resubmission of the automatically closed #202539.

Expected result

The homepage Contributors section should match the current default branch and REST contributors result.

Could a GitHub staff member rebuild or purge the stale Contributors/sidebar cache for this repository?

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

[monmoymondol]

Hi pnorman,

You can disable Copilot Code Review for a specific repository by adjusting its settings or permissions. Here’s how:

1️⃣ Repository Settings
• Go to your repository → Settings → Copilot → Code Review.
• Toggle “Enable automatic Copilot reviews” off.

2️⃣ Organization‑Level Control
• If your repository inherits Copilot Code Review from an organization policy, an org admin must disable it under Organization Settings → Copilot → Code Review.

3️⃣ Permissions Alternative
• Remove Copilot’s access to that repository by revoking its integration token under Settings → Integrations → Installed GitHub Apps → Copilot Code Review.

Currently, GitHub’s documentation focuses on enabling reviews, but disabling works by toggling the same setting or removing Copilot’s access. If you don’t see the option, contact GitHub Support — they can confirm whether your organization enforces Copilot reviews globally.

Once disabled, Copilot will stop generating automated comments on pull requests for that repository.