Share your ideas on how to improve SmartGit!


This is no support platform! To report bugs or request support, please contact us directly. If in doubt ask us.


First search for a similar request and add your votes or comments there.


Take the time to describe your request as precisely as possible, so users will understand what you want. Please note that we appreciate your time and input, but we don't give any guarantees that a certain feature will be implemented. Usually, a minimum requirement is a sufficient number of votes. Hence, please don't comment like "when will this be implemented", but vote instead.

Follow the stackoverflow.com writing guidelines.

Thank you for your help!

+2

code file diff in bracket pair colorizer

김병문 10 months ago 0


If bracket pair colorizer is supported, it will be easier to analyze nested parentheses when comparing and reviewing files.

JetBrains IDE supports it as a plugin, and Visual Studio and Visual Studio Code also support it natively.

And it is also supported by GitKraken, a market competitor.

If this is supported, analysis will be much faster in file difference comparison.

The screenshot below shows the bracket pair colorizer supported by Gitkraken.

Image 925

The bracket pair colorizer is supported in JetBrains IDEs if the following plug-in is installed.

https://github.com/izhangzhihao/intellij-rainbow-brackets

File compare
+2

Changes view: Remember "Ignore Whitespace"

rajiv 10 months ago updated by Thomas Singer 10 months ago 1

Please bring back the persistent "Ignore Whitespace" toggle. Since some build of 24.1, the "Ignore Whitespace" option resets every time I switch files, and I have to re-choose it constantly.

I spend a lot of time just viewing my working tree changes, and staging/unstaging hunks. Viewing significant code changes without the noise of whitespace deltas is important.

Therefore, I really want my viewing preference to persist. The new "Ignore WS" button is a welcome improvement, having it's state visible, and togglable with one click. (I would similarly welcome a "Ignore EOL" button 🙂). But constantly having to re-instate my preference, even just switching to another file then back, is tiresome.

Changes view
+2

Branches View: quick-search should support paste from clipboard and standard text editing features

Sergey Dyachenko 1 year ago updated by Thomas Singer 1 year ago 0

I found a very very strong drawback in your "Search for" form (appears not by hotkey or menu, but automatically as you type) in "Branches" View.
This form is absolutely incompatible with copy-paste!
Just try to find branch in "Branches" view using "Search for" and pasting required text from clipboard.
I tried several ways to workaround this strange behavior but everything did no work well.
If you type branch name manually - it works OK.
If you try to paste branch name or even part of branch name - it does NOT work.
Besides incompatibility of "Search for" with copy-paste from clipboard - it's also incompatible with standard text editing (for example, try to use left and right arrows to navigate in search text and edit it - your panel just disappears automatically).

My recommendation: allow user to make "Search for" permanent or show/hide it by explicit user request (not automatically - this works badly!) - at least it should NOT auto-destruct if I edit search text using standard text editing and it should work with copy-paste from clipboard.

Branches view GUI Log window
+2

Select two distant commits to compare

Marcel van Pinxteren 1 year ago updated by pgoiffon 10 months ago 2

Similar to `git diff <hash1> <hash2>` I want to select the first commit by searching in the log, mark it as "selected", then search the second commit, select it and do a compare. Alternatively, if a commit is selected, any commit can be clicked on to do "compare with selected". BeyondCompare has a similar behavior when selecting files from the Explorer.

Log window
+2

Allow "Move to" context menu to be hierarchical to match Repositories groups

Chris Jaquet 1 year ago updated by Daniel Siegl 1 year ago 1

We use nested groups to great effect in the Repositories view to manage our all our projects, often consisting of 100+ repos each. To arrange the repos in these groups we can either drag and drop into the group or use the context menu and choose "Move To".

With a hundred repos in a group dragging repos to another group does not work (in the past it would scroll slowly if you moved to the top/bottom of the view but this no longer appears to work) so we now use the context menu. The issue with the context menu is that it is a flat representation of all the groups. There are up/down arrows at the top of the context sub-menu but these only adjust the menu one line at a time which is also very slow.

My feature request is to make the "Move to" menu follow the same hierarchy as the groups in the Repositories view, using sub-menus rather than just spaces. This could be an optional feature enabled in config to not break other customers' workflows.

Some stats about my setup:

Number of repos managed by SmartGit: ~2800

Number of groups defined: ~210 (42 level 1, 146 level 2, 22 level 3)

SmartGit Details

Version: 23.1.3 #20195

Java version: 17.0.5+8-LTS (c:\program files\smartgit\jre)

Windows version: Microsoft Windows [Version 10.0.19045.4412]

GUI Repository Management
+2

Forgejo/codeberg integration

fourier 2 years ago updated by Daniel Siegl 1 year ago 4

For those of us who contribute actively to opensource projects based on forgejo(for of gitlab) platform, i.e. codeberg, it would be nice to have some sort of integration, i.e. referencing issues, query issues, list pull requests, etc.

+2

investigate diff should allow choosing commit rather that previous only

John 2 years ago 0

Currently, when investigating a file (right click file/investigate), the Diff view :

Image 828

only shows the diff between the selected file (New contents) and the previous version (Old contents).

It would be nice(r) if it was possible to select a previous version in the Navigation pane e.g:

Image 829

and have that replace the Old contents so one could compare (i.e. not unlike the functionality from using the working tree view and doing it there - just focused more in the Investigate window as then one is looking at the one file rather than the whole commit)

Investigate
+2

Specify which branch is going to be force-pushed

arcadius 2 years ago 0

It would be useful to see a name of the branch we're going to force-push.

Image 821


+2

File Log: filter files by the file

Clément Moyroud 2 years ago updated 2 years ago 5

When opening the file-specific log view and selecting two commits to show the diff, all the files modified between these two commits are shown. Since the intent is to look at the initially selected file, it would be much better if the filename was set by default in the filter, or maybe have an option to only show the logged file which would work across file renames.

Log window
+2

Add branch indicator for when behind master

Jeff Jensen 2 years ago 0

When a repo's master branch has incoming changes and the repo is checked out to master, SmartGit displays the helpful down arrow indicator. But, if the repo is checked out to a non-master branch, there is no indicator for the branch-to-master status (as the indicators are for the checked out branch). To learn if a repo's master branch has incoming changes to update and rebase my working branch on, I have to click on each repo to review it. This requires reviewing the graph to find those commits and see how they align - is the branch missing commits from master.

The current product I'm working on has over 20 repos. To help this, perhaps an indicator on a branch in the Branches view when the branch is behind on its master branch?