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

Add a copy Full commit data contextual menu entry

Michel Archambault 9 months ago updated 9 months ago 1

I would be nice to have an option in the contextual menu of a commit to copy the "Full commit data", similar the "copy to clipboard" -> "Full data" feature in Tortoise Git (and Tortoise SVN).

Log window
0
Completed

Add context menu item to set upstream of current branch

David Rees 9 months ago updated 9 months ago 2

It would be very handy if remote branch context menu had option to set the current branch's upstream. So user could create a branch, then right click the remote branch tile they want to track (which is usually there in the graph) to set the upstream.

Log window
0
Completed

Configuration option to define the name for the principal branch

Adhoniran Gomes 9 months ago updated by Marc Strapetz 9 months ago 1

The current Git convention is changing the principal branch name from master to main but SmartGit always create the principal branch named "master". If user want to use a different name to the principal branch a rename action is required after repository is created.

Please, add a configuration option to permit user configure any preferred name for the principal branch, then when a new repository is created, the preferred name is used, instead master.

Thanks for your attention and support,

0

Add option to specify repository and branch for "Push Up To..."

Martin Stolpe 10 months ago updated 10 months ago 1

When I create a local branch which doesn't track any remote branch yet and want to push the changes to a remote it would be nice if there was an option to select the remote repository and the branch.

Basically I would like to see this dialog, which is shown when I select "Push Up To..." in the branches view:

Image 865

also when I select "Push Up To..." in the logs view.

The behavior of "Push Up To..." differs between the different windows:

Working Tree Window + Log Window: A dialog is shown where I can push the commits and SmartGit will push the changes to a corresponding branch on the default remote

Standard Window: SmartGit directly pushes to a corresponding branch on the default remote

I often work with local commits where I have stored some local settings which I don't won't to push to the remote repository. That's the reason why I sometimes don't won't to push the complete branch to the remote repository.

Best regards

Martin

0

Fast Compare upper/below

shaidarov 10 months ago updated 10 months ago 1

Please add the ability to take all blocks above/below the current position in the File Compare interface


Image 863


File compare
0

GitHub Enterprise: support SmartGit as OAuth app

Martin Stolpe 10 months ago updated by Marc Strapetz 10 months ago 1

On Github Enterprise it is possible to register an app. In the dialog you have to specify a callback URL. If I understood it correctly this registration would be needed if I wanted to generate an access token from within SmartGit. If this is the case it would be nice if there was some documentation on how to configure this.

0

Use filter to show only tagged commits

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

It would be helpful to have an option that allows to reduce the complexity of the log graph by showing only commits that are tagged, or somewhat decorated (like head of branhces, etc.), still keeping branch and merge points visible.


In essence, the result should be what you get on the command line with:

git log --graph --simplify-by-decoration --oneline

That would make it much easier to grasp the history of repos that have long lived branches with hundreds of commits, which are seldom merged and tagged.

On the UI, this option could be a button/menu next to the filter text box, or could be triggered by a special "keyword" typed directly there, like "tagged" or "decorated" (with some special character perhaps? like #tagged or #decorated)

Graph
0

Actually filter when typing

Vojta Machacek 10 months ago 0

When I start typing and selection start jumping in the branches tree I would go one step further and actually filter the branches tree.. that way I can be better guided into finding what I'm looking for. 


Who ever worked with Jetbrains Rider or other IDE they know what I mean. Virtually EVERY list () can be quick-filtered on the spot which is very powerful. 

Image 862

0

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

Chris Jaquet 10 months ago updated by Daniel Siegl 10 months 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
0
Completed

Copy file name by Ctrl+Shift+C

arcadius 10 months ago updated by Thomas Singer 10 months ago 3

We copy full Commit / File name (with details) by Ctrl+C, and short Commit name by Ctrl+Shift+C.

Please realize copying short file name (i.e. filename only) by Ctrl+Shift+C.