this post was submitted on 13 Dec 2023
32 points (100.0% liked)

Git

2868 readers
2 users here now

Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency.

Resources

Rules

  1. Follow programming.dev rules
  2. Be excellent to each other, no hostility towards users for any reason
  3. No spam of tools/companies/advertisements. It’s OK to post your own stuff part of the time, but the primary use of the community should not be self-promotion.

Git Logo by Jason Long is licensed under the Creative Commons Attribution 3.0 Unported License.

founded 1 year ago
MODERATORS
Ategon@programming.dev
jnovinger@programming.dev
canpolat@programming.dev
32
Every engineer should understand git reflog (graphite.dev)
submitted 10 months ago by canpolat@programming.dev to c/git@programming.dev
4 comments fedilink hide all child comments
top 4 comments
sorted by: hot top controversial new old
[–] swunchy@lemm.ee 8 points 10 months ago (1 children)

I know when I have to go to the reflog that I've really fucked up

[–] sik0fewl@kbin.social 2 points 10 months ago

You haven't really fucked up until you've run garbage collection.

[–] jnareb@programming.dev 4 points 10 months ago

One thing that is not made clear in the article, is that there is a separate reflog for HEAD, and separate reflogs for individual branches.

HEAD reflog logs changes such as "checkout: moving from next to main". Branch reflog logs changes such as "branch: Created from HEAD" (first entry in branch reflog). Most are common to both (i.e. git logs both to HEAD reflog and the reflog of currently checked out branch).

[–] onlinepersona@programming.dev 3 points 10 months ago

Learned something new today. Thank you.