Yeah but... What happens when you work with a new college who put two features in a branch because he forgot to switch and someone did a shitty review and it's now in master but you can't revert because its release day and three other colleges already did a rebase and you cannot take the time to revert this mess anymore because other bugs and...
I mean commits in need of repair happens, however good your workflow is.
That's why new members of the team get extra attention for their first few changes, PRs require two reviews, and we don't rebase master.
I've really just never needed to do major repairs to the master branch of a project I was working on. We're probably missing out on git features that could be nifty, but it's also easier to avoid shooting ourselves in the foot.
I mean commits in need of repair happens, however good your workflow is.