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

Add mode to Reset menu name; optionally with a Preference to choose default mode

MattD 3 years ago updated by Thomas Singer 3 years ago 1

Users coming from Atlassian SourceTree are used to Mixed being the default. And, I almost never use hard reset, though others clearly do.

It would be clearer if the reset menu's name included the mode. So instead of "Reset.." it would say "Reset (Hard).."

It would also be convenient to have a preference that changes the mode of the "Reset.." menu. If you did both of these suggestions, the "Reset.." menu name would change based on the selection.
0

Edit the message during interactive rebase using the enter key

Iulian Onofrei 3 years ago 0

If you rebase interactively, and need to edit the message of multiple commits, you have to use the mouse to double click the entries, because pressing enter starts the rebase, even though cmd + enter starts the rebase too.


Instead, you could use enter (edit commit message) > reword > enter (to confirm the message) > down arrow > enter (edit commit message) > etc., which would be a lot faster.

0
Completed

Disable file name tooltips when navigating between changes in multiple files

Iulian Onofrei 3 years ago updated by Thomas Singer 3 years ago 1

When you use the next change button with multiple files in the working tree (or in a commit), a temporary tooltip with the file name shows up right in the middle of the changes, so it obscures some of them.

It would be nice if you would be able to completely disable them, since the file name is already displayed in 2 different areas of the current window.

0
Completed

Spell check the current word, too

Iulian Onofrei 3 years ago updated by Thomas Singer 3 years ago 1

The last typed word is never spell checked, not even after a pause. This means that a typo in the last word of a commit message is never underlined, so, easily missed.

0

Manage git tags for different remotes

Patrick123 3 years ago updated 3 years ago 1

Currently I can see the git tags in the branches window on the same level as "Local Branches" or any remote.

I have the situation, where I have the exactly same tag name on different remotes. The remotes contain related history and are all added to one local git repository.

It looks like Smartgit only shows the tags for 1 of the remotes and I can't figure out, (within SmartGit) which remote contains which tags.

It would be great, if Smartgit could display all tags from all remotes.

One solution would be to show the tags within the corresponding remote or to show the tags in a similar style like it is done for remote branches with the same name (Remote1/Tag1, Remote2/Tag2 etc.).

0

gitconfig/others: support negative refspec

thojo 3 years ago updated by Marc Strapetz 3 years ago 0

Support for negative refspecs would be great. It seems SmartGit does not understand it's syntax yet because I get an "Command Failed - Invalid wildcards ^refs/heads/something-to-exclude/*" error when using them.

See Stack Overflow and implementation.

0

Standard Window + simple Workflow: Locking Support, "open file dialogue" and stash Capability

Sascha P 3 years ago 0

Hi guys!

Wanted to congratulate You on the simplified views for 22.1!

As someone who is responsible for supporting users of varying git-knowledge, it is greatly appreciated that You are taking steps towards making Git more accessible to the uninitiated. ;)

(I for one would be very glad to get rid of our tertiary, error prone Git GUI, that we use for training purposes primarily, and which has striking resemblance to this new view ;))

Some Remarks from my side:

Our document-engineers needn't concern themselves with advanced git stuff, but would like to see:

* Ability to lock and unlock office files

* Open files from within GUI

* When they realize they forgot to lock, they should have the ability to stash changes before pull

Within standard view + simple workflow, these are not possible currently.

As a bonus, it would be nice for them to see the locking status of documents before attempting to lock.

Currently, You have to configure pull operation to fetch lock status. This is not something that the average user expects.

BR, Sascha

0

Tools should support env-variables in Command

Mario123 3 years ago updated by Thomas Singer 3 years ago 1

Using external tools in Smartgit could be greatly improved for us using templates for new accelerators which accepts system-env vars as command inputs.

e.g.: %LOCALAPPDATA%\Programs\Microsoft VS Code\Code.exe 

as a command value is not being processed by smartgit.

0
Completed

Show progress for Filtering Content during clone [SG-15033]

Alpaka 3 years ago updated by Marc Strapetz 3 years ago 1

When cloning a repository, SmartGit shows a nice progress-bar, except for the step "Filtering content", which is usually quite fast, but in my example, it took several minutes. Not knowing, whether SmartGit hung up or not, I force-closed the application and cloned the repo from the command line.

It would be great to show the progress and that something is still going on while the clone operation is filtering content.

Image 655

instead, the UI gets stuck here for a very long time:

Image 656

Answer
Marc Strapetz 3 years ago

What kind of filter is this? Git-LFS?

0
Declined

Make it possible to add an empty folder to a repository

Markus2021 3 years ago updated 3 years ago 4

Allow to add an empty folder to a repository and put that under version control. This is useful if somebody wants to define a folder structure to be used by some other developer but has no contents yet for these folders as that content shall be generated by the other developer.