Comment by Zardoz84
and git commit --fixup git rebase -i --autosquash
and git commit --fixup git rebase -i --autosquash
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
? 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.
> 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)No need to make a "backup" branch. Learn to trust the reflog.
My human inputs are usually commit messages like "awdjhwahdwadga" until I do the rebase at the end
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.