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!

+1

Conflict Resolver: another view on conflicts

sergey ivasenko 1 month ago 0

The only thing that i find often inconvenient in SmartGit - the way conflicts are displayed and handled in Conflict Resolver.

SmartGit view:

Image 956

JetBrains GitClient view:

Image 957

The later has much more clear (and less scaring :) LOL)  picture of the conflicts.

Would be perfect if we are able to switch to yet another view on the conflicts that would be similar to the one on the second screenshot!

Thank you!

Conflict Solver
+1

Create GitHub pull request also from Worktree Window

auchri 1 month ago updated by Daniel Siegl 1 month ago 1

At the moment it is only possible to create a GitHub pull request from the log window. Please also implement this option in the working tree window

Working Tree window
+1

Branches view: show local branches first

Andy Hughes 2 months ago updated 3 weeks ago 3

In the branches section, add the option to sort all local branches to the top of the list.

Image 954

Branches view
+1

Changes view: remember "Ignore Whitespace" option also for local files

oozing-blade 4 months ago updated by Thomas Singer 4 months ago 0

When traversing changes either in working tree or stage, SmartGit resets "Ignore Whitespace" toggle after switch to next file back to default state which is untoggled.

This is to emphasise not missing unexpected or other kind of important w/s changes.

However from time to time one would need to traverse files quickly, to skim through changes at glance which is often not possible when w/s are highlighted.

I'm unsure how to approach the solution. E.g.: low lever setting for reset behavior, put it to hamburger menu of diff window, diff setting, double click on toggle would make it permanent, …

Image 949

Image 948

Image 950

Changes view
+1

Standard window: Tree view option in Files View

oozing-blade 5 months ago updated by Thomas Singer 5 months ago 0

File Views lacks Tree View option. When validating code changes not only code is checked but also files structure and files placement.

When file path gets obscured by ellipses having tens (or hundreds) of files it gets quite impossible to validate placement, replacements or movements of files is correct.

Image 945



Simple, classic, tree view would come handy for these cases.

Image 946

GUI Standard window
+1

Fixup a past commit and rebase autosquash

Cyril DD 5 months ago updated by Jeff Jensen 5 months ago 1

Ability, when committing changes, to fixup a past commit (if there are no merge conflcts for subsequent commits)

Suppose I have committed 

A > B > C 

..in that order. I realize I missed something on commit B, if I want to fix it I have to introduce a new Commit D, and make an interactive rebase to move commit D so it becomes A > B > D > C and merge commit B and D (we often refer to part of this process as a fixup)

I suggest improvements to the smartgit interface to be able to perform this automatically. Note that this procedure is now facilitated by the --fixup param when committing as explained here

Idea : in the commit window, we already have a "select" menu that can help copy previous messages. Introduce a similar "fixup" select menu, which allows selecting a commit similarly to "select", but when a previous commit is selected this way, transform the "commit" button so it becomes a "fixup" button and actually performs

git commit --fixup=[selected commit ref] # Commit indicating a fixup
git rebase -i --autosquash [selected-commit-ref]~1 # merge fixup commit into broken commit

(ans similarly for the other button "fixup and (force) push"

Image 941




References

https://stackoverflow.com/questions/3103589/how-can-i-easily-fixup-a-past-commit

Improve Git commands
+1
Started

Working Tree Window: Bring back alternating row colors

CodeStorm 6 months ago updated by Thomas Singer 6 months ago 1

At least as of v21.1.x the Working Tree window used alternating table row colors for the various files displayed. Could that be brought back in the current version(s), either as a setting or property of some sort? Or is there a way to do it already in the current version somehow?

Thanks,

Image 939

Working Tree window
+1

Branches view: Multiple branches-views with pre-defined filters

InD84 6 months ago updated 6 months ago 4
Situation
There are thousands of branches in hundreds of groups with “path-like names”. It is very tedious to find the branchs you want in the branches-view (The overview is miserable). And most of the times you are only interested in the branches of a handful of subfolders anyway.


Of course, you can also press CTRL + P and then enter the relevant subfolder to quickly see the desired branches. But unfortunately this is also very cumbersome if you want to merge the respective branch into your current branch:

  1. You have to click into the branches-view.
  2. You have to press CTRL+P and enter the subfolder you are looking for (and rememeber those names).
  3. YouI have to select the desired branch. (Unfortunately, in this view you don't have the option to merge the selected branch with your current branch).
  4. So you have to reveal the branch.
  5. Finally you can merge the desired branch into your current branch.


Desired behavior:

I would like to define a filter for the branches-view and attach the filtered view as a separate tab in Smartgit (with a self-defined title). This way we could have multiple tabs for the branches-views (each with different filters and title).


Not only would this greatly improve the overview, but it would also reduce the number of steps that need to be taken:

  1. Click into the filtered branches-view and select the desired branch.
  2. Merge the desired branch into the current branch.

Branches view GUI
+1

Totals in Files Window

oozing-blade 8 months ago updated 8 months ago 1

It could come useful to have totals for commit in Files view.

I.e. counts: total, renamed, changed, removed, added.

Image 928

+1

Changes view: Remember "Ignore Whitespace"

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

Please bring back the persistent "Ignore Whitespace" toggle. Since some build of 24.1, the "Ignore Whitespace" option resets every time I switch files, and I have to re-choose it constantly.

I spend a lot of time just viewing my working tree changes, and staging/unstaging hunks. Viewing significant code changes without the noise of whitespace deltas is important.

Therefore, I really want my viewing preference to persist. The new "Ignore WS" button is a welcome improvement, having it's state visible, and togglable with one click. (I would similarly welcome a "Ignore EOL" button 🙂). But constantly having to re-instate my preference, even just switching to another file then back, is tiresome.

Changes view