I used git CLI for merge squashing, then resorted to SmartGit for rewiewing changes/committing.

(I thought maybe SmartGit could read the default commit message from .git/SQUASH_MSG or similar).

git merge feat-branch --squash => git commit works in this way, i.e. it pre-populates the commit message with the squashed commit messages. Would be nice if SmartGit could do the same.

Fits well with a guideline of having full URL and not only issue number.

From https://robots.thoughtbot.com/5-useful-tips-for-a-better-commit-message

"5. Consider making including a link to the issue/story/card in the commit message a standard for your project. Full urls are more useful than issue numbers, as they are more permanent and avoid confusion over which issue tracker it references.

This is generally done as the first paragraph after the summary, on line 3."

+1 for highlighting matches, makes several related commits (e.g. issue number) to be more easily distinguishable in the log
(similar to Notepad++ :

Ok bummer, thanks for the feedback :) (I imagined something like generating 3 temporary files while waiting for the external process to complete and then read and save the temp files for index/work area upon exit code 0).