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!

0
Completed

Files View: default Ctrl-c to filename instead of row data

Jeff Jensen 4 years ago updated 4 years ago 5

I regularly copy the file name from the Files view which means using the context menu as Ctrl-c maps to copy the row data.  This request is to map Ctrl-c to copy the filename instead.


Since this request causes a breaking change, perhaps can create a low-level property with a list of options to map to?


Additionally, I always paste and then remove the extension, so my desired choice is map Ctrl-c to filename without extension.

0
Completed

Option to disable "Ignore as pattern" in Ignore dialog

Chris Jaquet 4 years ago updated 4 years ago 4

Please can we have an option to disable the automatic selection of "Ignore as pattern" in the ignore dialog:

Image 549


For the screenshot I have exactly one file selected and it is a C++ header. SmartGit defaults to selecting a pattern for all headers which means it is really easy (and has happened on a number of occasions at my company) where a developer accidentally ignores all new headers in a git project. Quite often this is only discovered during evening automated builds which fail due to missing files.

I would like an option to make the the default always "Ignore explicitly" forcing the user to think about whether they want to ignore the pattern. I would rather have very long ignore lists than accidentally not commit something that should not be ignored.

Some backgrounds: we have a number of tools that automatically generate C/C++ code within the source tree (for technical reasons) and we add these files explicitly to the ignore list for the various repositories.

0
Completed

Discard: "Discard to Stash" button should not be the default

mtancoigne 4 years ago updated by Marc Strapetz 4 years ago 12

When discarding changes, the highlighted button is "Discard to stash". I think it would be a better choice to highlight "Discard" and switch button positions, as it's very misleading. I don't know for others, but when I want to stash files, I use the corresponding action, and when I want to discard things, I want to... discard things.

Having the option to stash instead of discarding is a good idea, but it definitively should not be considered as "default"

0

Make the font size of the whole application configurable

Max Alekseyev 4 years ago updated by Thomas Singer 4 years ago 2

Can I make SmartGit GUI size bigger?

0
Completed

ctrl + p and ctrl + shift + p should support fuzzy search

Matthias Traunsberger 4 years ago updated by Thomas Singer 4 years ago 1

I love the search panels that open on ctrl+p (cmd+p) or ctrl+shift+p (cmd+shift+p), but the search algorithm could be improved.


Let's say I want to search for a branch called "feature/abcd-1234_description_blablabla". I can type "feat", or "1234", or "descr", or "bl" and the listing will show the branch I'm looking for.


I'm not able to enter multiple search token separated by space. I would like to be able to enter "fea<space>1234<space>descr" and still seeing the branch I want. For me, it would be fine/expected that the single fuzzy search tokens are compared as starting strings and not substrings, e.g. I would not expect my branch to be found, when I search for "fea<space>escription", but when I type "fea<space>desc". But this could be a setting in the preferences.

The order of my search token should not matter regarding whether a branch or tag is listed or not.

0
Completed

GitHub/others: option to hide comments in the Log window [SG-13853]

ubruhin 4 years ago updated by Marc Strapetz 4 years ago 3

I like the GitHub integration mainly for one reason: To fetch Pull Requests (instead of manually pulling from other remotes) so I can review them in SmartGit since IMHO it is a way better diff viewer than the GitHub webinterface.

But if the GitHub integration is enabled, obviously comments on PRs are fetched as well and are displayed in the Log diff viewer. This is quite disturbing the review (lines of other text appear between the lines of text to review), so I'd like to hide them.

Unfortunately I didn't find an option to hide comments. Or am I missing something? Actually I'd even prefer to completely disable comments globally - they don't even need to be fetched during the GitHub sync.

0

Option to not open a new copy of SmartGit when the current one is busy.

Nick Hustak 4 years ago 0

I frequently open another window of SmartGit because I don't notice it's busy when I go to open another repository.   It's incredibly annoying.  Could we get an option to simply toast a message that it's busy rather than open a new copy of SmartGit?

0
Completed

Graph Date Display

Dale 4 years ago updated by Thomas Singer 4 years ago 3

In the graph window, would it be possible to change (or make in an option to change) the date display from the day name (e.g. Thursday, Friday) to the actual date? The window does do this for commits older than a week (06/30/20 instead of Monday). The issue is, when looking at older screen shots (in a meeting or presentation) nobody knows what Thursday or Friday means.

Thanks!

0
Completed

SmartSynchronize blank comparison

My-Tien 4 years ago in SmartSynchronize updated 4 years ago 2

A comparison window with blank views where you can simply drag and drop text in to compare with each other – like in Meld – would be very nice.

0
Completed

Hide low priority branches

Stephen Leach 5 years ago updated by Thomas Singer 4 years ago 0

I am often working on repos with a large number of branches (>400). I would like the ability to mark branches as low priority and to hide them in the branches pane.