Ready to merge" button stuck loading until page refresh

[MadhivananR]

🏷️ Discussion Type

Bug

Body

I have noticed an issue while working with Pull Requests on GitHub.

After creating a Pull Request and waiting for all checks to complete successfully, the "Ready to merge" button continues to display a loading state instead of becoming available automatically. The merge button only appears and turns green after manually refreshing the browser page.

Steps to Reproduce
Create a Pull Request.
Wait for all required checks/statuses to complete successfully.
Observe the "Ready to merge" section.
Notice that it remains in a loading state.
Refresh the page manually.
The "Ready to merge" button immediately becomes available.
Expected Behavior

Once all required checks have completed, the "Ready to merge" button should automatically update and become available without requiring a page refresh.

Actual Behavior

The "Ready to merge" button remains stuck in a loading state until the page is manually refreshed.

Environment
Browser: Microsoft Edge / Google Chrome
Operating System: macOS
Repository Type: Private Repository
Occurrence: Multiple times across Pull Requests
Additional Notes
Refreshing the page consistently resolves the issue.
It appears to be related to the GitHub UI not updating the mergeability status in real time.
Please let me know if additional logs, screenshots, or a screen recording would be helpful for troubleshooting.

Thank you for looking into this issue.

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