Lost git commit after rebase & force push - post git object removal

Question

I ran the below command to fix the this issue:

find .git/objects/bd/4e31f16fc91fdc25b4b8e50c16c6f12422d467 -size 0 -exec rm -f {} \;

After that when I force pushed my code after rebasing & squashing older commit, everything is lost and pull request got closed automatically erasing all commits. There is no way I can get back my code from whatever I know. The commits have vanished.

Is there any way to get back my committed code?

Does someone else had same commits? Do you have disk backups? Have you tried disk recovery tools on .git folder? — Moti Korets, Apr 12 '19 at 09:35
@MotiKorets No it was my branch. I am trying to get the files from IDE history. — JavaYouth, Apr 12 '19 at 09:49
Try disk recovery tool for .git repository looks like its the only chance.. — Moti Korets, Apr 12 '19 at 11:08

score 1 · Answer 1 · answered Apr 12 '19 at 16:11

pull request got closed automatically erasing all commits

If this pull request is done on GitHub, then GitHub support would still be able to restore those commits, erased by the forced push.

Through the GitHub API, you can even yourself query the past push events, performing a "poor man reflog".

But regarding local commits, check first your git reflog.

Lost git commit after rebase & force push - post git object removal

1 Answers1