As noted in the documentation, git reflog takes an action verb (called <subcommand>) and optional modifiers. The action defaults to show, and its optional modifier is the reference name to show. The default is to show operations on HEAD. (Most, but not all, “everyday” commands operate on and/or through HEAD in order to operate on … Read more
On the off chance that the remote machine is a github repository, First use Github’s Events API to retrieve the commit SHA. curl https://api.github.com/repos/<user>/<repo>/events Identify the SHA of the orphan commit-id that no longer exists in any branch. Next, use Github’s Refs API to create a new branch pointing to the orphan commit. curl -i … Read more
git log shows the current HEAD and its ancestry. That is, it prints the commit HEAD points to, then its parent, its parent, and so on. It traverses back through the repo’s ancestry, by recursively looking up each commit’s parent. (In practice, some commits have more than one parent. To see a more representative log, … Read more
Maybe it’s too late to post a reply, but as this page is the first Google’s result, it may still be helpful. If you want to free some space in your git repo, but do not want to rebuild all your commits (rebase or graft), and still be able to push/pull/merge from people who has … Read more
Before answering, let’s add some background, explaining what this HEAD is. First of all what is HEAD? HEAD is simply a reference to the current commit (latest) on the current branch. There can only be a single HEAD at any given time (excluding git worktree). The content of HEAD is stored inside .git/HEAD and it … Read more
Per the man page, you can use git log options, e.g., git reflog –pretty=short git reflog –date=iso