Stale contributor remains in repository sidebar after history rewrite #204830
🏷️ Discussion TypeBug BodyStale contributor remains in repository sidebar after history rewriteRepository: I rewrote the repository history and force-pushed all branches and tags to The current state has been verified:
Stale sidebar endpoint: Could GitHub staff please invalidate or rebuild the repository homepage Thank you. |
Replies: 3 comments
|
💬 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 ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
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. ⭐ |
|
Your cleanup actually worked everywhere except that one cached page fragment — I checked from the outside:
So the data layer is clean; the only stale piece is the Two realistic options:
Given you've already verified the graph data is correct, a ticket with exactly the evidence you posted here should be quick to action. |
|
Update: I contacted GitHub Support as suggested, but the ticket was automatically The repository data remains clean:
Since there appears to be no user-facing cache invalidation mechanism and Thank you. |
Your cleanup actually worked everywhere except that one cached page fragment — I checked from the outside:
/repos/randian-2008/bilibili-music-player/contributors) already returns onlyrandian-2008(33 commits).refs/pull/*refs keeping the old commits alive (those can sometimes pin rewritten history, but not here).So the data layer is clean; the only stale piece is the
contributors_listhomepage fragment, which is a separately cached, lazily rebuilt UI component. There's unfortunately no user-facing action that forces it — pushes, renames, and settings toggles don't inval…