Yeah learned this the hard way.

you are viewing a single comment's thread
view the rest of the comments
[–] 7 points 1 year ago (6 children)
  • [–] 18 points 1 year ago (5 children)

    Think of it like your browser history but for Git. It’s a list of the SHAs related to your recent operations.

    And because Git is a content-addressable data store, a SHA is basically like a URL. Even if a branch no longer exists, if you know the SHA it pointed to then you can still check out the exact contents of that branch. The reflog helps you find that.

  • source
  • parent
  • hideshow 5 child comments
  • [–] 17 points 1 year ago (4 children)

    Goddamit... It's ref log, not re flog. I thought this was related to blame and never touched it lmao

  • source
  • parent
  • hideshow 4 child comments
  • [–] 3 points 1 year ago (2 children)

    Re flog is when your devs don't follow your guides and mess uo git history again.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 1 year ago (1 child)

    I legit thought it was to publicly call out a user to be (metaphorically) flogged

    And while it's not how I do things, I totally understand the impulse. Tell me that doesn't sound like something that could exist

  • source
  • parent
  • hideshow 1 child comment