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!
When multiple commits selected in log view, "select mutual ancestor"
I often want to know what commit is the most recent shared ancestor for two commits.
Suggestion: when more than one commit selected in Log view, add "Select Mutual Ancestor" to popup menu. This would unselect the selected commits and then select (and show) the most recent commit that is an ancestor of all selected commits (as "git merge-base" would).
Stage button in File Compare window
in File Compare after you're done with take left/take right, you have a Save button, would be nice if you also had a Stage button next to the Save button
Remove settings for older SmartGit versions
SmartGit maintains a settings directory for each used major version. Hence, when upgrading SmartGit, settings directories of previously used SmartGit versions remain. When launching SmartGit in a non-preview mode with a registered, valid license, it could offer to delete settings directories from previous versions.
Gitlab Merge Request; if fetch, immediately enable display
If there's a new Gitlab Merge Request, and you use "Fetch Merge Request" to fetch it, it should be by default displayed (with the checkbox checked).
Move stash with drag'n drop
In graph view, I would like to grab a stash and drop it on top of another commit.
This would "rebase"the stash.
This helps keeping stashes linked to a branch after rebasing this branch.
Rebase feature branch onto older revision of master
Let's say, I have a feature branch b1 based on branch master. After rebasing it to the newest version of master, I realize there's a problem and want to go back. But I cannot rebase b1 onto an older revision of master because the path from the new base commit to my feature branch head includes the commits of master.
Currently, I create a new branch at the new base commit and cherry-pick all the commits of my feature branch. That works but requires to create a new branch with a new name.
I'd propose to add a rebase option that allows to choose the branch to be rebased (maybe only visible if there's the need for it). Rebasing then starts with the first commit of that branch. If there is a sequence of branches (b1 based on master, b2 based on b1, and so on), smartGit could offer a list to chose from.
Scaling UI -- ui.dpiFactor -- open the options, it's just math
Currently, there are 2 options 1(100%) or 2(200%)
This is not flexible at all. With many form factors for monitors, I would like more control so I can fulfill my specific need.
For me, 100% is too small 200% too large, yet those are the only options
Why not allow the input of actual percentage or multiplication factor i.e. 1.5
fyi - using windows application scaling does not work as smartgit does not act the same way other applications work. If I scale the system prefs to a viable size every application UI but smartgit is too large
please give me the scaling flexibility for my specific monitor
Add more info to Output window
Pull (Rebase)
Pull (Rebase)
Pull (Rebase)
Pull (Rebase)
Pull (Rebase)
Pull (Rebase)
Push
Push
Commit
Commit
Push
Pull (Rebase)
isn't very helpful.
Please add the repo name in there too so we don't have to expand everything to see what was actually changed.
Customer support service by UserEcho
