5 ms·

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 1y ago
  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
  • trenchpilgrim 1y ago
    My human inputs are usually commit messages like "awdjhwahdwadga" until I do the rebase at the end
  • lloeki 1y ago
    > 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 1y ago
      No need to make a "backup" branch. Learn to trust the reflog.
      • deleted 1y ago
        [deleted]
      • lemonlearnings 1y ago
        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 1y ago
        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
  • lemonlearnings 1y ago
    ? I assume you want to replace your jubberish messages with something more useful before pushing? It is only "destroying" https://xkcd.com/1296/ https://xkcd.com/1296/ style crap? Code changes stay the same.