[lemonlearnings]

Claude, look at this git history, analyse diffs and create an intelligent commit message to replace each commit message. Do a rebase to fix it all up.

[kristopolous]

Would you actually do that? It's information destruction. You can machine generate at any time, but you can only delete the human input once

[lloeki]

> you can only delete the human input once

    git branch "backup/$(git branch --show-current)/$(date +%s)"
    # do whatever you fancy
    git reset --hard "backup/$(git branch --show-current)/${thattimestampabove}"

You can't lose anything as long as you have a pointer to it (which doubles as making it easy to find)

[globular-toast]

No need to make a "backup" branch. Learn to trust the reflog.

[lemonlearnings]

That is like learn to trust the indestructibility of matter. I can still lose (not able to locate...) my keys even though they still exist!

[lloeki]

reflog doesn't keep things through gc.

the only thing that does keep a git object is having a ref that (directly or transitively) points to it

[trenchpilgrim]

My human inputs are usually commit messages like "awdjhwahdwadga" until I do the rebase at the end

[lemonlearnings]

? I assume you want to replace your jubberish messages with something more useful before pushing? It is only "destroying" https://xkcd.com/1296/ style crap? Code changes stay the same.