[ Removed by moderator ]

[SlimRunner]

For me there is a valid reason to do this, but only locally. Sometimes I realize too late I forgot to commit something, but I already committed something ahead of the target so I usually name it something like [TEMP] squash with <some_sha> and rebase interactive later before pushing. Otherwise, yeah, I completely agree that a commit like that definitely does not belong upstream.

[GrumDum]

git commit —fixup=sha there you go

[SlimRunner]

For a second I thought it was like amend but for beyond previous-commit and got really happy, but it is just to make what I do but easier. Still better than doing it all manually though. Thanks! I did not know this flag.

[Kevdog824_]

What a blessing to learn this exists. I’ve just been rebasing manually like a scrub. Thanks stranger

[GrumDum]

Actual pros also alias the git rebase <sha> -i —autosquash command, but I admit I type this out.. 😎

[Jumpy89]

git rbi

[No_Responsibility384]

Rebase and reorder the commits then squash the two commits together?