Pull request won't synchronize after moving the changes from master to a different branch, then back #180175
-
Select Topic AreaQuestion BodyHi, I have a pull request at PixelGuys/Cubyz#2141 that is closed because I moved the changes from master to a different branch. I then realized that I can't change the branch of the pull request, so I put the changes back on master. But now the pull request can't be opened again. I already tried pushing an empty commit without luck. Is this a bug or how can I fix this? Is this the right place to ask something like this? |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments
-
|
Hi friend 👋 This isn’t a GitHub bug — it happens because the pull request’s base and head commit history no longer match what GitHub expects. ✅ How to fix it GitHub won’t allow reopening the old one because the commit history changed and doesn’t match what the PR was originally based on. |
Beta Was this translation helpful? Give feedback.
-
|
This isn’t a GitHub bug. A pull request can only be reopened if the head branch still contains the exact commit history that the PR was originally created from. That’s why the “Reopen pull request” button is disabled — GitHub no longer considers the branch compatible with the original PR. How to fix it:
Once the commit history diverges from what the PR was based on, GitHub permanently blocks reopening — it’s expected behavior, not a bug. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you both |
Beta Was this translation helpful? Give feedback.
Hi friend 👋
This isn’t a GitHub bug — it happens because the pull request’s base and head commit history no longer match what GitHub expects.
When a PR is closed, GitHub will only allow reopening if the exact branch history still matches the original state. Because you moved commits between branches and rewrote history, GitHub now sees the PR as outdated, so the “Reopen pull request” button stays disabled.
✅ How to fix it
The only real solution is to create a new pull request with your updated master branch:
1.Make sure your master branch contains all the changes you want.
2. Push everything to GitHub.
3. Create a new PR from your master to PixelGuys/Cubyz.
GitHub won’t allow reopening th…