I don't think you can do it with reflog.
However, you can use git fsck --lost-found. This command will give you all dangling blobs and commits.
After the command, check the .git/lost-found folder.
In a "hello world" project with a few commits it can be cool... however on a big project it will give you hundred of files π
Is there a way to tell, from the
git reflog
view, that the third commit is orphaned?I think there is a way. The term is βan unreachableβ commit. I donβt know the commands though.
I don't think you can do it with
reflog
.However, you can use
git fsck --lost-found
. This command will give you all dangling blobs and commits.After the command, check the
.git/lost-found
folder.In a "hello world" project with a few commits it can be cool... however on a big project it will give you hundred of files π
πgit-scm.com/docs/git-fsck