https://plugins.jetbrains.com/plugin/7566?pr=idea

Given the recent slew of vulnerabilities in gpg (gpg.fail), al well as several years of recommendations by security experts (latacora, soatok), I'm currently phasing out gpg. In alternative to gpg, git also supports signing commits with SSH keys (gitlab, github).

It would be great if SmartGit could support SSH signatures.

Current-workflow: copy-file → leave-SmartGit → file-manager-navigation → find-target-repo-directory → paste → return-to-SmartGit → stage-changes. Friction-heavy.

Proposed-feature: right-click-file → Copy-to-Repository → dropdown-shows-all-local-repos → select-target + choose-destination-path → automatic-transfer.

Result: file-copied-to-target-repo (new-file, no-history-attached) -- source-repo-unchanged, history-preserved.

Use-cases:

• config-file-sharing across projects (eslint, prettier, workflows)
• component-migration between codebases
• template-distribution to multiple repos
• cross-project-asset-syncing

Benefit: workflow-stays-in-SmartGit → no context-switching → faster-iterations → cleaner-mental-model

Current-workaround: terminal-cp-commands OR file-manager-juggling -- both break-flow.

This-feature → treats-repos-as-connected-workspace rather than isolated-silos.

Any chance of showing all the timestamps in UTC?
communicating with a team across the Atlantic, sometimes I'd like to talk about commits (a commit-hash is pretty darn specific) but having a correct universal way of stating a time would also be helpful.

When clicking the pull toolbar button while using the log graph startup window, it opens up another window requiring another click to do the pull.  It would be nice to have a dedicated pull button that only requires one click.

For a Github repo that requires mandatory signed commits for PRs, the feature of background AI-generated commit messages (i.e. just putting "@ai" or "WIP" as message) is not usable as the final commit with the generated text is not signed.

Currently multiple repositories are organized by manually arranged groups on the "Local Repositories" tab. For my multi-repo workflow, I usually end up working with several clones clustered in directories that have all their dependencies together for an active task. This means that I might have multiple `foo` clones in various commit states on my disk. Because of this, it is often hard for me to tell which `foo` repo corresponds to which directory with the current SmartGit multirepo management system.

Rather than having things manually arranged into groups, it would be helpful to have a button that just sorts all the SmartGit-tracked repositories into collapsible file trees that match the directory structure on disk. This would be independent of the current manually user-defined groups which I can see as having distinct logistical value for some workflows.

Originally, I thought that this was how it worked, because on first install, that was how all the manual groups were configured. However, subsequent repository additions have required me manually dragging the files in the right place. This is kind of tedious, especially if I batch clone a bunch of repos from the command line and want to add them later into SmartGit.

If this proves too invasive to have independent options, I would be satisfied with an automated solution to sort the manual groups to match the directory structure. 

Loving SmartGit, by the way! Such a huge improvement over SourceTree!

Current Behavior:

SmartGit’s Changes pane currently displays the unchanged file content twice when only a file’s permissions have changed. However, it does not show the actual mode difference (e.g., 100644 → 100755), making it difficult to audit permission changes without switching to external tools like the Git CLI.

Proposed Enhancement:

Display the exact file mode change inline in the Changes pane, such as:
File mode changed: 100644 → 100755

This should appear clearly above or alongside the diff view when no content changes are present.

Benefits:

• Improves visibility of non-content changes
• Helps developers catch unintended permission toggles
• Reduces reliance on Git CLI for metadata inspection
• Enhances trust and transparency in cross-platform workflows

Currently the color contrast between the searched text and the background for added content is really bad and thus it took me 2 minutes just to find where the `next find` is pointing at. Please update this to take into account the background color so it "pops" at me and tell me where to look at.

At the moment it is only possible to create a GitHub pull request from the log window. Please also implement this option in the working tree window