Merge check gets stuck indefinitely #152284
Replies: 5 comments 7 replies
|
💬 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. ⭐ |
|
Check for Large Diffs: If your branch has a substantial number of changes compared to the main branch, GitHub might struggle to compute the mergeability, leading to the hanging message. In such cases, consider breaking down your changes into smaller, more manageable pull requests. |
|
FTR hit that bug today twice in a row, without a big diff merge. |
|
Got a similar issue, will try what mxmehl suggested |
|
This issue is still present. I have a PR that has only 14 commits so the large diff is not the problem. The PR has been hanging since this past Tuesday. Doing commit amends and force-pushes doesn't solve the issue. I don't want to close the PR and open a new one if it doesn't solve the problem. Would it be possible for the GitHub developers to add some form of button so that if someone experiences the hang, then the button could gather and report the exact circumstances that is causing the hang? This is very frustrating! |
Uh oh!
There was an error while loading. Please reload this page.
Select Topic Area
Bug
Body
When merging down from main with the "Update branch" button, I see the error below and the "Checking for the ability to merge automatically..." message and spinner persist indefinitely.
occurred on this PR
Same behavior with the old merge experience

occurred on this PR.
Closing and re-opening the PR does not fix. The only fix is opening a new PR with the same branch which of course is not a good flow.
All reactions