Comment Comment by Yasuraka Did you mean reflog?Either way, even simpler, imho, than any log that one has to comb through after the fact is to create a named backup branch=$(git branch --show-current) && git switch -c backup-${branch} && git switch - Carry on as planned and if you bork it all, switch to the backup branch which retains the original commits and all, delete the borked one and have another go git switch backup-somebranch && git branch -D somebranch && git branch -m somebranch parent Yasuraka 2 years ago
Either way, even simpler, imho, than any log that one has to comb through after the fact is to create a named backup
Carry on as planned and if you bork it all, switch to the backup branch which retains the original commits and all, delete the borked one and have another go