Commit dialog does not allow adding any other column such as Last Changed.

A helpful feature would be the ability to mark certain commits with a color, making them easier to find and revisit later.

When traversing changes either in working tree or stage, SmartGit resets "Ignore Whitespace" toggle after switch to next file back to default state which is untoggled.

This is to emphasise not missing unexpected or other kind of important w/s changes.

However from time to time one would need to traverse files quickly, to skim through changes at glance which is often not possible when w/s are highlighted.

I'm unsure how to approach the solution. E.g.: low lever setting for reset behavior, put it to hamburger menu of diff window, diff setting, double click on toggle would make it permanent, …

Set an option to only show merge requests if user is Reviewer or Assigned to it.

As someone who thinks Conventional Commits is a noisy and useless convention (which the tagging should have been relegated to the body as a parsable format like `@type chore`), is it possible to allow a custom hook or script for users to pre-process the git log?  

The hook method also allows the user to do whatever they want (e.g. remove JIRA IDs), so I think it will be very flexible.  If usage becomes widespread, SmartGit can even promote some of these internally through a filter.

Performance might be an issue since it needs to be executed on every message, but since it is opt-in, it wouldn't affect 99% of users.

And just like any filtering, I guess there needs to be an indicator for when the filtering is in effect.

Hi,

When I want to merge my feature/fix branch to main branch I have always the check box "create simple commit (squash)" unchecked.

It will be usefull if there is a configuration to do to say :

• Check "create simple commit (squash)" by default when merge.
• Or check "create simple commit (squash)" by default when merge with a main branch (we can also assume that there is a configuration to identify a main branch list).

Thank you,

Karim

Hello,

Features which help user to learn hot keys becoming more and more popular. This can be seen by increasing popularity of IDE plugins which implement this feature.

So my suggestion is to implement same logic here. When user perform actions not by using keyboard shortcuts new popup should be shown with information about hot key combination which can be used instead.

Cheers,
Volodymyr

Hello!

Please consider adding extra coloring to new commits which appear in the Journal after rebase (successful or unsuccessful). Maybe for pull as well.
After rebase its hard to visually track which commits were added to history to review/investigate.
Adding extra coloring will be very helpful. It can be added for some short period or until some operation or permanently.

Thanks,
Volodymyr

Improve user experience when working with complex multi repository projects.

Terminology:
- git repository container - folder which may be git repository folder or may contain other git repository containers

Use case:
- there is main folder which is git repository container
- structure may contain repeated names

Why existing features does not work:
- Search for repositories - allow you to find for nested git repositories and import them. Not sure it can handle duplicate names (when path is different). Also (what is more important) it flattens the structure cause it does not open folder itself it open separate git repositories within a folder.

Suggested approach:
- When 'Repository > Add directory' is opened - show dialog to open a directory

- Dialog should allow you to select existing folder

- When you click 'OK' selected folder will be added to the list of open repositories
- If selected folder is a git repository it should be treated as regular git repository
- If selected folder is a git repository container - it should be marked as such (with different color or whatever). Same applies to nested folders if they are git repository containers

Enhancement:
- Add 'import as groups' check:
- - When not checked - will open folder as git repository or git repository container (see previous section)
- - When checked - if directory is:
- - - regular git repository - create new group, add git repository to this group
- - - git repository container - add new group, add all nested git repository containers as nested groups, add all nested git repositories to corresponding groups

Alternative:
- Enhance existing "search for repositories" feature allow adding them as a tree as well

Thanks for your attention

s. sorry for not using lists unfortunately your formatter is not good enough and just couldn't format text properly

Although it is obviously intended behavior: when selecting one of the options mentioned above it should be remembered or at least be configurable. It is frustrating to change this option each time when you launch smartgit. The fact that it is now intended behavior is a decision that i.m.o. does not focus on the customer.
Having this configurable would make smartgit a more user-friendly.