OK. I have updated the title and description.

I would limit the marker check in code only to those lines which you have modified. So, only if you are modifying a line which already contains such a marker from previous commits, that would result in a false-positive warning.

For myself this check would work better than an explicit action in SmartGit, because I'm already using such TODO-markers anyway (e.g. IntelliJ IDEA has special support for them) and thus there is zero overhead to have such a check working. If I had to switch from IDEA to SmartGit and invoke some additional operation there, that would be cumbersome.

Is this something which could be told from the diff of the file? E.g. because the diff contains markers like "TODO"?

For version 20.2, there will be Low-Level Property "log.graph.denoteSignedCommits".

I have remove the other issue "More, before, if I uncheck privacy option "Use gravatar.com to show images for the users", at Commit window, the avatar image can hide. But now, it always shows." from this topic. Please create another topic, if necessary.

What about the Branches view, should Sign-symbols be hidden there, too?

That's unexpected, if "credential.github.com.useHttpPath" is configured. Can you please check Preferences, Authentication see to whether SmartGit actually stores multiple passwords, one per repository?

Are you aware of current workaround? https://www.syntevo.com/doc/display/SG/GitHub+integration#GitHubintegration-Authenticatingwithtwoormoreaccountsmultiple-accounts

Present in 20.2 Preview.

> > The fetch will be triggered exactly once the Changes view tries to access blob data... which is triggered by the Graphselection.

> 

> Ah, just tried - I see what you mean. I think I was thinking of the 20.2 Preview 1 feature that allows the Changes view to auto-hide behind the Graph view and come to the front only when a file is selected. With that enabled, I think it would be good to not fetch until the Changes view is brought into focus (ie, by a Files view selection or by manually clicking the Changes tab).

>

> This allows quickly perusing the Log for details other than the diffs (eg, parent/child commits, detailed commit message, etc), but still smoothly seeing diffs when needed. Do you agree?

I agree, that sounds like an optimization which could even be done independently. I have logged this as SG-13950.