[bug] Cherry Pick, Append source to commit message - doesn't append, instead overwrites message

[goran-w]

When I do a Cherry Pick from a commit and select the following options...

• Commit all changes = No
• Append source to commit message = Yes

...then I'd expect the message from that chreey-picked commit to be appended to any existing message in the commit-message box.

Instead, any existing message is overwritten with the message from the cherry-picked commit.

Next, I'd expect to be able to gather multiple cherry-picks into a single new commit by repeating the above process (before I make any commit). That doesn't work as expected, since for each new cherry-pick the previous message gets overwritten.

To summarize, I'd like to to multiple cherry-picks in sequence and have all the corresponding commit-messages appended to my upcoming commit message, including any initial message that I had begun writing for changes I made before the first cherry-pick. No previous message should be overwritten but only appended, until I'm ready to make my single commit (consisting of a few "stacked" cherry-picks and possibly some other "manual" changes).

[love-linger]

When Append source to commit message is checked, SourceGit just enable the -x option to git cherry-pick command.

[goran-w]

That's hard to understand from the wording of the option. (Also, the minimal '-x' tooltip should probably say 'Git option: -x', to be more explanatory.)

For the use-case I describe, it would be much preferable to actually append messages, rather than to overwrite - the latter is a "destructive" action, where I risk losing a "just started" commit-message, and on repeated cherry-picks (without immediate commit) I'll lose also the previous cherry-pick messages.

From a user perspective, being able to combine / interleave (potentially multiple) cherry-picks with other changes (into a single commit) is a great feature - but it needs a more complete "append" feature to really support this use-case.