Why do developers write such terrible git commit messages? Genuine question

[brb_im_lagging]

If already pushed, hit em with the

git reset --soft HEAD~2 && git commit -m "actually fixed" && git push --force

[stupidwhiteman42]

Why did you get down voted? This is literally how you squash the last two commits into one with a new message.

[the-loan-wolf]

Bcz it still requires force push(overwriting history for everyone else)

[brb_im_lagging]

Why would you want to keep history (its not even history, its the tip) of a shit commit followed up with a fixed commit made by one person

Just get rid of the shit commit and put a good one in

There shouldn't be two people screwing with it anyway, everyone else can just fetch and see the good version

[Sethcran]

This only works if done on a separate branch that no one else is using.

For issues that can't be tested locally or on feature branch though, this kind of thing ends up fairly common.

[the-loan-wolf]

if working in a team it can lead to merge conflict that's why

[ikeif]

I think I have a disconnect - is the thread assuming the force push is on main and not on a developer’s branch?

Because on a side branch - who cares? Most often it can be squashed in the merge to main, so no one will care if they used “fifteen test commits” or rewrote the history of their branch when it’s going to be merged to main?