GitHub Community
Issue: Pull Request Stuck in "Checking for ability to merge automatically" Status Hello GitHub Community, #130262
Replies: 15 comments 33 replies
|
Hello, I've encountered this issue before and understand how frustrating it can be. Here are some steps you can try to resolve the problem:
For a more detailed discussion and additional troubleshooting steps, you might find this Stack Overflow post helpful: https://stackoverflow.com/questions/63315676/github-how-to-solve-hanging-pull-request. If none of these steps work, consider reaching out to GitHub support for further assistance. They can provide more in-depth analysis and support for your specific situation. I hope this helps! |
|
yes, Github is having slowdown in PRs merging |
|
I think it's happening again, whie github status is still green |
|
Same thing happening here... Edit: Seems to have resolved itself after 10 minutes. |
|
Also encountering the issue. Its been stuck over an hour |
|
Having same issue right now. Status page (someone should really mention the link in this discussion😂) all green. Update: Recovered after about 5 minutes. |
|
Happened again, Github status page shows it's fully working. 
What's the point to use those rules if we can't have a stable platform to use? |
|
This same issue happens to me, for the first time as well 🤔: 
Perhaps the GitHub Status website (at this point in time) is totally green. Even in the |
|
me too, really funny when I saw your comment as now XD |
|
lol same time |
|
update: the issue's just gone after waiting for some time, not sure what's happening though |
Solution
In my ciase I don't need to create branches. |
|
Today it happened to me for the first time. What I did. Closed pull request, and created a new one totally same and it works fine now. |
|
same here. Status looks ok |
|
experiencing same issue for about 20 minutes already. Tried solutions proposed here - nothing works. |
|
same! |
|
Same here |
|
Same here. Still hanging, even with no additional checks to run... It's been that way for a while now... |
|
same |
|
I see same error |
|
Just blame it on github and move on |
|
One possible cause (NB this solution won't be relevant for some users) is if your repository has errors in its To see if this affects your repository firstly navigate to the 
Then your 
One possible error that can occur if you've recently transferred a repository between organisations (or changed user permissions) is that all users in a In the above example the repository in question had recently been transferred between GitHub organisations and some users were previously inheriting write permissions from the old organisation but after transferring a repository they no longer had write permissions on it. After granting the affected users write permissions on the repository my 
|
|
I don't have this CODEOWNERS file. |
|
i have the same probelm and i dont have a CODEOWNERS file |
|
This was just one solution I ran into for my version of the problem, I have updated my answer to make it clear that this won't be the cause of/solution to the problem for all users |
|
This happens to me all the time. Lately about 90% of all merges. However, if I wait 5 seconds and reload the browser page, it always continues and completes the check. |
|
I have the same problem now. It starts one or two weeks ago. If I open the same url in a new browser it's ready! It seems to me, that only the website didn't get the update? 
But the two checks get their updates: |
|
Experiencing this today.... Annoying. |
|
using the CLI worked for me (i.e. |
|
Not sure if its OK - but I just do a re-load...Then its all green and ready to be merged. |
|
For me, what worked was simply making a new commit. |
|
Do we even need this check? We can just hit merge and if it fails later with a conflict, it fails. This is impacting productivity by inserting unnecessary friction. Please fix this. |
|
This has been happening to me on a regular basis, only reloading the PR page numerous times fixes this |
and others
Hello,
I've encountered this issue before and understand how frustrating it can be. Here are some steps you can try to resolve the problem:
Ensure that all the required status checks are completed. Sometimes, additional checks (like CI/CD pipelines) might be running in the background. You can find this information in the "Checks" tab of your pull request.
Sometimes, updating your branch with the latest changes from the base branch can help resolve the issue. You can do this via the command line or directly on GitHub by selecting "Update branch" if available.
For a more detailed discussion and additional troubleshooting steps, you might find this Stack Overflow post helpful: https://…