Back when I used SVN, we had TortoiseSVN which when you where about to enter the commit message you were able to recall the last commit message with the up arrow key if the textarea was blank. This was a very handy feature when you were commiting a series of related changes (for example: "User CRUD UI: Fixed race condition", "User CRUD UI: Fixed button margin", etc.). You just pressed "up" and the previous message was there for you to edit. :-)

I would like to rename my stash after I created it.

This stackoverflow link shows how we can do it with git commands mnually:

https://stackoverflow.com/a/35549615/3328979

On large repositories, SmartGit performs sluggishly compared to command-line git when doing refresh operations. 

This makes the experience of working in SmartGit frustrating in large repos, because SmartGit performs refresh operations frequently (e.g. after pulls, after certain failed push operations, when the window comes to the foreground, etc).

As an example, we have a repo containing approximately 254,000 files. Here are the results comparing SmartGit ("17.1 preview 7 #11051, installed: #11019") versus Git for Windows ("2.12.2", 64-bit).

Initial refresh after startup ("cold cache" test):

• SmartGit: 24 seconds
• Command line: 2.5 seconds 

Subsequent refreshes of same repo:

• SmartGit: 14 seconds
• Command line: 1.5 seconds 

In these tests, SmartGit is consistently 9-10x slower than command-line git.

Perhaps this is because SmartGit is (last I checked with Syntevo) using the java-base jgit library for all read-only operations. 

Significant work has been put into command-line git over the past year (especially by Microsoft itself, which now uses git as their own internal source control on major products like Windows itself). 

It's a shame that SmartGit does not take advantage of these improvements to make the SmartGit experience as snappy as the command line one.

If someone sends me code and I commit it, I want to list them as the author but it seems only possible to edit the commit after the fact.

Hi,

Relative to the thread https://groups.google.com/forum/#!topic/smartgit/3w46shCd_mg it could be nice to have the "key" icon for all signed commit (like for signed tags). The static key color could be replaced with green or red key to have a quick look of the GPG key integrity/verification.

Instead or alternatively to the hard limits which can be configured in the Preferences by Show line length guides, the commit message textareas could do some highlighting on the text, like VIM does, allowing us to format our commits like the Linux standard: titles of 50 char at most, one empty line, description below.

This is supported by GitHub by giving you a short-desc and long-desc fields, and warning on 50chars+:

When you push a branch to a remote, the Push To dialog does not show the branch name. I'd love to have that so when I'm using the keyboard I'm sure I'm not pushing the wrong branch.

Would be nice to allow formatting commits in the window according to conventiona-changelog format.

https://www.conventionalcommits.org/en/v1.0.0/

Support for possibly huge "mono repositories", by:

• offering a "shallow" clone of the repository
• selectively fetching projects from the repository, using Git's "sparse checkout" feature and "partial clone" feature
• limiting Log graph (and dependent views) to such a fetched project

Support should be implemented in a subtle way to not complicate the GUI for the majority of "plain" repository users.

Related topics:

• Partial Clone Support
• Sparse Checkout Support

Please comment on this topic about your monorepo size:

• Number of projects
• Number of commits overall (git rev-list --all --count)
• Number of files in HEAD overall (git ls-tree -r HEAD | grep -c "")

Not selecting any file, both cmd + k and cmd + s commits, respectively stashes all the files in the working tree.

Selecting one or more files from the working tree, cmd + k commits them while cmd + s stashes all the files, in which case the selection is completely ignored.

This is not consistent and, at least for me, very unintuitive. A lot of times I selected some files, hit cmd + s, and pressed enter, only to see that all the files were stashes instead.