Why does a Git commit seem to be missing from the branch I expected?
Quick answer
A commit may be on a different branch, have been made while HEAD was detached, or be outside the history range you are viewing. Start by checking git branch, then inspect recent history with git log --oneline -n 20 and review git reflog. These checks can help locate the commit before you change references. Reflog entries are local, and their availability depends on what the repository recorded. [S1] [S2] [S3]
The question, the details, the next step.
I made a commit, but it is not showing on the branch I expected. What should I check first?
Start with read-only checks; avoid commands that change branch or commit references while you are still looking for the commit. Run:
git branch
Then inspect recent history:
git log --oneline -n 20
Compare the branch you expected with the one you are on, and look for the commit in the log. The log command is limited to 20 entries here, so not seeing the commit in that output does not by itself show that it is lost. Git history commands can display different commits depending on the references and range selected. [S3]
The branch name is not what I expected. Could the commit be on another branch, or did I commit without one?
Either is possible. A commit made on another branch may not appear in the branch history you expected. Also, git branch indicates detached HEAD state. In that state, HEAD identifies a commit rather than a branch, so a commit made there may not appear in the expected branch history. [S1]
Use git branch to orient yourself, then compare the branch names and recent commit IDs shown by the history you are inspecting. Keep this as an investigation: the goal is to identify where the commit appears before changing any references.
I can’t see it in the recent log. How do I tell whether I’m looking at too little or at the wrong range?
Check the exact command or history view you used. Note which references it starts from, whether it specifies a range, and whether it limits the number of commits shown. Git’s log range affects what appears: for example, git log A..B lists commits reachable from B but not A. A commit can therefore be absent from a particular display without that alone meaning it is lost. [S3]
As a simple next check, use a larger limit:
git log --oneline -n 50
If you know the suspected commit ID, compare it with the IDs shown. Remember that increasing the limit does not change which references or range the command uses. If you used a range before, inspect that range rather than assuming the shorter output covered all relevant history.
It still isn’t there. What does the reflog tell me, and what should I do if I find the commit?
Inspect the local reference history with:
git reflog
Reflogs record updates to local branch and other reference tips; the HEAD reflog also records branch switching. Its entries may help you locate a commit or position that is no longer the current expected tip. Reflog history is local, and what you can find depends on the entries recorded in this repository. [S2]
Look for an entry around the time you committed or switched branches, and note its commit ID. Before attempting recovery, verify that it is the commit you intended and decide which branch should contain it. The checks above help locate evidence; they do not move the commit onto a branch. If you are unsure about the next step, get someone familiar with the repository to review your plan before changing references.
A practical checklist
Run
git branchand check whether you are on the expected branch or in detached HEAD state. [S1]Inspect recent history with
git log --oneline -n 20; note that the output is limited. [S3]Check the exact references, range, and display limit used by your history view. [S3]
Review
git reflogfor local reference updates and branch switches. [S2]Before attempting recovery, verify the commit ID and decide which branch should contain it.
A few more useful answers
Does not finding a commit in a log display prove it is lost?
Is the reflog a shared record for everyone using the repository?
No. Reflog history is local to the repository; its entries are not a shared record. [S2]
Should I change a branch as soon as I find a likely commit?
First confirm the commit ID and decide which branch should contain it. Locating a commit is an inspection step; changing references is a separate recovery step.
Sources
References used for this guide.
- [S1] Git User Manual: Detached HEAD git-scm.com · Checked
- [S2] Git - git-reflog Documentation git-scm.com · Checked
- [S3] Git - git-log Documentation git-scm.com · Checked