sublime_merge icon indicating copy to clipboard operation
sublime_merge copied to clipboard

Data loss when editing a commit message

Open haferburg opened this issue 1 year ago • 1 comments

Repro:

  • In a commit history with commits A followed by B, edit the earlier commit message A, but don't Save.
  • Select A and B, Edit Commit -> Squash (fixup)
  • A and B get merged, and the edited commit message is lost forever. There is no warning.

My workflow is to commit something with a placeholder message. Then edit both the message and the content as I'm progressing through development.

I've lost data countless times because of this behavior. It's the worst part of Sublime Merge.

It should just preserve the edited commit message. When I'm doing fixup, I don't care about the other messages. At least it should ask if it's ok to delete data.

Alternatively, don't do this Edit/Save thing. It's 2023. Just let me edit the message, commit it to history when I'm done. Or provide an auto-save option.

haferburg avatar Jul 07 '23 17:07 haferburg

It just happened again. It's 18:35. I want to go home. Yet Sublime Merge makes me type a long commit message again.

This time I edited one commit message, then switched to the parent commit, edited the commit message, clicked Save, which results in SM destroying the edited message of the child commit.

Please do something about this.

haferburg avatar Dec 11 '23 17:12 haferburg