GitHub Pull Request count is always one too many after merging

[peterwwillis]

Select Topic Area

Bug

Body

If you have 3 open PRs, and you merge one, the "Pull Requests" tab at the top of your browser window says "3", when it should say "2". If you shift+refresh, it goes to "2". So there's a bug in caching this number.

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

[tanmaysinghx]

Bug: Stale PR Badge Count (Cache Sync Issue)
This looks like a stale state in the browser's local cache or a failure in the Live Updates (WebSockets) push for that specific tab. Since a Shift + Refresh fixes it, the browser is likely holding onto a cached fragment of the navigation bar instead of re-validating the count after the merge redirect.

Possible Culprits:

Service Worker Caching: The UI is pulling the navigation header from a local cache that isn't being invalidated on the POST request to merge.

Missing Event Listener: The merge action is successfully updating the DB, but the "broadcast" to update the UI badge isn't being triggered (or received) by the open tabs.

Temporary Workaround:
Hard refresh (Cmd/Ctrl + Shift + R) or clicking the "Pull Requests" tab directly usually forces a re-fetch of the metadata.