Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
@b4n I added you as a collaborator, let me know if there are any problems.
Here you go, that PR is restored and should match what you had in #1241,
You can now push whatever you need (including force-pushing if necessary) and it should properly update this PR.
I had some trouble with step 2
fatal: bad object 1e9a8b0c32d15c27ba448e689545c0bc5c9b97aa fatal: the remote end hung up unexpectedlyI'm a bit out of my depth but I'm willing to learn. Where does that hash come from?
1e9a8b0 was the commit this PR was at (as seen in the commits history before I force-pushed, and as you can see in the force-push notification above). The idea was to restore the branch to the state it had when this PR was closed so GitHub sees it as matching this PR, and accept re-opening this PR. If you didn't have that hash anymore, it means that Git's garbage collection got rid of it on your end (as it was an old commit not referenced by anything anymore); you could have gotten it back by fetching it from GitHub (as I did myself, git fetch asifamin13 1e9a8b0c32d15c27ba448e689545c0bc5c9b97aa).
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.