oh wow this is super useful
> --fixup=reword:<commit> creates an "amend!" commit which replaces the log message of <commit> with its own log message but makes no changes to the content of <commit>.β€Œgit-scm.com/docs/git-commit#Do…

#git #gitRebase #gitFixup #gitAutosquash
Git - git-commit Documentation

The reason this is so useful is because I will look at a big rebase and go oh, that commit in the middle should be renamed. So I mark it for rewording.

The rebase runs and suddenly I'm supposed to reword a commit. What was this about again?
Oh, so this is new! This arrived in the latest git, 2.33.0.

Normal people: What's wrong with the git 1.8 that ships in CentOS 7?

Me: oh no I only have git 2.29 yessss conda-forge now has git 2.33 install install
@clacke i won't touch git earlier than 1.9, which is when they introduced some git ref tricks I use a lot. (Or maybe it just fixed a bug, i don't exactly recall)
@klaatu Can't fetch non-tip commits in 1.8, that's one thing I know. Maybe that's in 1.9.

I've fallen in love with --rebase-merges and that's from probably last year, maybe around 2.20.

There's something else in my aliases that breaks on < 2, can't remember what, but if it's in my aliases I probably use it every day.
@klaatu What are the ref features you use? I don't think any mode of reference I regularly use is newer than The Beginning Of Time in 2005.