This looks like git commit --amend, only more difficult to remember.

But --amend only works for the last commit. This is for any older commit in your history. Like fixing a typo 4 commits ago.

Good point, I read "previous commit" as "parent commit".

It could probably written more clear. I also usually prefer to do this task with a manual "edit" in the interactive rebase. Usually because I want to test if stuff works at that point after the change. And it is much more transparent than using "magic fixups" :)

Good point, I read "previous commit" as "parent commit".

@tomaszzielinski I added some explanation to "previous"

It could probably written more clear. I also usually prefer to do this task with a manual "edit" in the interactive rebase. Usually because I want to test if stuff works at that point after the change. And it is much more transparent than using "magic fixups" :)

@oderwat Yes, I always use simply git rebase -i and manually squash , edit or pick commit. I didn't know this magic fix-up until yesterday. It is nice to test at that fixup point, but if one test the fix-up before rebase and has confidence in himself 😉 , he can use this approach to quickly solve the problem.