Some PRs still missing on repositories page after failure several months ago

[Mingun]

🏷️ Discussion Type

Bug

Body

A few months ago, GitHub reported an incident due to which some PRs may have left invisible. At that time, there was a notification about this on the pages with a request not to worry, because nothing is lost and restoration work is underway. At that time I was just going to the https://github.com/serde-rs/serde/pulls/Mingun page and was very surprised to see a lot less PR there than I did. Currently, I am still not seeing these missing PRs. The page above shows only 6 open PRs, although there should be 3 times as many.

Example of invisible PR: serde-rs/serde#2811. I was able to find it only by attempting to create PR for that branch again, then GitHub shows that PR already exists: https://github.com/serde-rs/serde/compare/master...Mingun:serde:visitor-driven?expand=1.

Views, affected by this bug:

• https://github.com/serde-rs/serde/pulls/Mingun
• https://github.com/pulls/authored

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

[ndevenish]

Similar behaviour seen on out https://github.com/dials/dials. I filed a ticket (#4486780) a few days ago that hasn't had a reply yet.

These PR show up via the api e.g. gh pr list which we have fallen back on.

Edit: See Also: https://github.com/orgs/community/discussions/193463

[Mingun]

Thanks for pointing in the right direction. When I created a ticket in GitHub Support following the instructions from this thread, they reindexed serde-rs/serde in several hours.

So, while generally the problem is probably not solved (should not contact support for each such case) in my case it is solved thanks to you.

[ndevenish]

Great, I should also update that they did indeed fix manually after a couple of days!