![]() ![]() ![]() ![]() It’s great that you can see this information but what use is it to us, you ask? Remember that git branches are just pointers. These lines can be broken down into 4 parts: commit hash, commit pointer, action, and extra info. checkout: moving from wickedfeature to master pull origin bugfixI: Merge made by recursive.Ĩ518f9d. commit: Add more cowbell to foo.cĦdbc22d. pull origin bugfixJ: Merge made by recursive.Ĩ54d44e. pull origin featureA: Merge made by recursive.Ĥ9d0608. pull origin featureB: Merge made by recursive.Ĥ9d0608. If you run git reflog right now in a repository you’ve been working in, you’ll see lots of changes that look something like this: c5c3a82. The only time commits are actually deleted is if you git gc -prune (so be careful with that one!). You can always get back to any repository state as long as you committed your changes. When you use git, commits are never lost. Have you ever committed something, tried to git rebase, and everything went horribly horribly wrong? Or accidentally git reset -hard HEAD^ when you meant to git reset HEAD^? Have no fear, git reflog is here! ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |