robertpainsi/README.md

Last active June 12, 2026 20:23

Star (201) You must be signed in to star a gist
Fork (30) You must be signed in to fork a gist

Select an option

Learn more about clone URLs
Clone this repository at <script src="https://gist.github.com/robertpainsi/2c42c15f1ce6dab03a0675348edd4e2c.js"></script>
Save robertpainsi/2c42c15f1ce6dab03a0675348edd4e2c to your computer and use it in GitHub Desktop.

Download ZIP

How to reopen a pull-request after a force-push?

Raw

README.md

How to reopen a pull-request after a force-push?

Precodinitions

You need the rights to reopen pull requests on the repository.
The pull request hasn't been merged, just closed.

Instructions

Write down the current commit hash of your PR-branch git log --oneline -1 <PR-BRANCH>
Write down the latest commit hash on github before the PR has been closed.
git push -f origin <GITHUB-HASH-FROM-STEP-2>:<PR-BRANCH>
Reopen the PR.
git push -f origin <HASH-FROM-STEP-1>:<PR-BRANCH>

Example

You've a PR branch my-feature currently at 1234567. Looking at the the PRs page, we see that the PR was closed when my-feature pointed at 0abcdef.

git push -f origin 0abcdef:my-feature #pushing the old commit the PR has been closed with
Reopen the PR.
git push -f origin 1234567:my-feature #pushing the latest commit

Gammal-Skalbagge commented Apr 23, 2021

very helpful and easy to find. thank you!

iMonZ commented Sep 2, 2021

Thank you so much, you saved my day!

chadthompsonallscripts commented Oct 5, 2021

When you do a soft reset in order to squash commits, then forget to commit and force push the branch, it closes the PR with this error. Thank you for this, as with everyone else here, I'll chime in that this saved the day.

jswny commented Oct 25, 2021

Amazing 🎉

heesuk-ahn commented Nov 22, 2021

Thanks your sharing!

akbortoli commented Dec 13, 2021

Thank you for sharing.

JemarJones commented Jan 7, 2022

Thank you for the tip!

Ed6ar commented Mar 3, 2022

Thanks master.

damiendillon commented Mar 17, 2022

Thank you!!

mochadwi commented Jun 22, 2022

Thank youuuu!

Mirko-Weiler commented Jul 3, 2022

Thanks!

natalia-tamy commented Oct 3, 2022

Thank you so much!

allblueee commented Feb 12, 2023

thx! life saver!

sqiuChime commented Feb 24, 2023

👍 👍 👍

omarY23 commented Mar 20, 2023

Thanks alot!

ayeankit commented Mar 22, 2023

Thanks a lot. This saved my day.

sumayaSalihs commented Mar 29, 2023

Thanks a lot. This was so helpful.

pljones commented Apr 19, 2023

Brilliant! Thanks!

hinell commented Apr 22, 2023

How come that devs at github fucked up so hard, so we have to push/pull forth and back just to make PR working?

koenigr commented Jun 13, 2023

Thank you very much !!!!

jw3215 commented Jun 16, 2023

Thanks a lot !!!

zyqxd commented Jan 3, 2024

This issue essentially is due to your PR and your origin branches having mismatching histories (caused by a force push after that PR closed). If your PR has multiple commits, you may need to reset the entire branch. For example

If your PR commit history is:

sha-0123 <- head
sha-1234
sha-2345

But your origin branch history is

sha-3210 <- head
sha-4321
sha-5432

You need to do reset your origin head to sha-0123, then force push your new history head to sha-3210:

# if you don't have commit `sha-0123`;
git fetch sha-0123
git co FEATURE-BRANCH
git reset sha-0123 --hard
git push --force
# **You should be able to reopen your PR at this point**
# reset to `sha-3210` on the same branch
git reset sha-3210 --hard
git push --force