CODEWITHSUNDEEP
gitbranch
Dan Rosenstark
Dan Rosenstark

Reputation: 69777

Scare of My Life With GIT: I've got no branch!

I had checked out an old hash (commit) and was working on it, checking in merrily and ignoring warnings that I wasn't working in a branch. Then I switched to a branch and realized that I had no way to get back to my orphaned checkins (luckily I had the terminal window open still, so I checked it out and branched).

How can I get GIT to tell me the names of the commits that do NOT belong to a branch? Or just all the commits, if that's not possible...

Upvotes: 6

Views: 613

Answers (3)

John Stoneham
John Stoneham

Reputation: 2483

See this question which has a great explanation of how to find stashes you've dropped. You can see dangling commits etc. the same way.

Upvotes: 2

jamessan
jamessan

Reputation: 42697

git reflog will show the log of the references created by recent activity you've done. For future reference, git checkout of a commit puts you on an detached head. If you want to base work on an old commit, you should create a branch off of that commit instead.

git checkout -b newbranch oldsha1

or

git branch newbranch oldsha1
git checkout newbranch

Upvotes: 7

Andrew Aylett
Andrew Aylett

Reputation: 40730

You can fish them out of the reflog, which stores the commits which you've had checked out.

git reflog will print out the most recent commits pointed to by HEAD, which is your working copy.

You can also get a list of all objects in your tree which are unreachable from your current branches using git fsck.

Upvotes: 2

Related Questions