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!
Add support to show commit details during interactive rebase
During an interactive rebase the main window is not accessible.Therefore it is not possible to access the graph and to get commit specific information (files which changed and file diff support). Therefore a large rebase process could be very annoying if only the commit message is visible / accessible.
Add a copy Full commit data contextual menu entry
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).
Open multiple repositories in explorer
Sometimes I want to open multiple repos (6-15) in windows explorer from the Repository view in the LogGraph view. Therefore I have to right click each one and say "Open in Explorer". It would be nice if that option would also be shown if you select multiple repos which would then of course open also multiple explorer instances.
Add context menu item to set upstream of current branch
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.
Configuration option to define the name for the principal branch
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,
Add option to specify repository and branch for "Push Up To..."
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:
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
Fast Compare upper/below
Please add the ability to take all blocks above/below the current position in the File Compare interface
GitHub Enterprise: support SmartGit as OAuth app
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.
Use filter to show only tagged commits
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)
Actually filter when typing
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.
Customer support service by UserEcho