Many Python users work with virtual environments (venvs), typically one per project. For pre-commit hooks to run correctly, the appropriate venv must be active; otherwise, issues such as missing modules can occur (e.g., Pylint will report "module missing" errors if the wrong venv is being used).

A workaround that currently can be used is to launch SmartGit via scripts individually crafted per project to activate the respective venv, e.g.:

call C:\Users\username\PycharmProjects\project_name\.venv\Scripts\activate  
C:\Apps\SmartGit\bin\smartgit.exe  

However, this is not a general solution, since SmartGit allows users to switch between projects within the tool, which leads to the wrong venv being used again. It would be great if there was a way to have Smartgit automatically activate the correct venv of the respective project.

Especially when pre-commit hooks are active, commits can take a couple seconds. Would be helpful to be able to abort the commit if you realize that you do not actually want to perform this exact commit while waiting for hook execution.

The "Log Window" and "Working Tree Window" allow flexible customisation of the layout, so why not the "Standard Window"?

The left sidebar uses a lot of dead space, taking the entire height, and I can't see checked-out branches and stashes at the same time.

I want to give some of that dead space to the Changes view, ideally the full width of the window (I prefer side-by-side diffs).

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.

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!

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