Details
-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
None
-
None
-
Severity 3 - Minor
Description
When I pull new changes for a submodule, I get a change entry for that submodule in the containing repository. Then when I stage that, I need to remember why I'm even pulling in these changes to compose the commit message.
It would be great if SourceTree could grab the commit messages for that range and pre-fill my commit message field with them.
Or offer to grab them, like when I merge in changes and it offers to paste in the merged commits' messages. SourceTree knows the current and new hash already (it shows it for the change entry, after all).