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!

+3

GitLab: option to open merge request in browser

PL Sarbakan 6 years ago updated by Marc Strapetz 6 years ago 0

An option to open a merge request in gitlab (browser) would be very useful (to reply to comments, etc.)

+3

Add Open in GitHub to context menus

Ed Ball 6 years ago updated by rsignup 5 years ago 1

I would like to see "Open in GitHub" in the context menu for just about everything: repositories, folders, files, remotes, branches, tags, and commits.

+3

Align chunks in compact change display

Zeblote 6 years ago 0

Here's a random commit from Unreal Engine as an example why this would be useful:

Image 311

You can see how it's somewhat clunky to read, it gets even worse with larger differences.

Much easier when it's aligned!


Image 312

+3

Remember multiple window instances with positions and opened repositories

Bugged 6 years ago updated by Thomas Singer 1 year ago 0

For example, if you have the Google Chrome setting `Continue where you left off`, enabled:

Image 309

And you exit Google Chrome with `File -> Exit`, or you computer just crashes (i.e., abruptly restarts), the next time you open Google Chrome, it restores (i.e., opens back) all opened windows and tabs.

Currently, if I have 2 Working Tree opened, each one with a different repository and I do `File  -> Exit` with SmartGit, the next time SmartGit reopens, it will open back only one (1) window, with the 2 repositories opened.

This behavior is not desired because if I had two (2) windows opened, each one with a different repository open, I would like for SmartGit to keep it that way, the next time I open it.

It also would be nive if SmartGit can:

  1. Restore my two (2) opened windows, in case my computer crashes (i.e., abruptly restarts)
  2. Also restore any Log Window, in case I had one of them opened.
GUI
+3

Commit window: show current user

Andreas Schneider 6 years ago 0

I often switch between work and private PC and on each between work and private repositories. It therefore happens that I sometimes accidentally commit with my private email address to a company repository or vise versa.

It would be nice to see the current user (name and email) you commit with in the commit dialog to avoid such situations.

+3

Output window: more flexible text selection

chuvv 6 years ago updated by HFloyd 3 years ago 6

Instead of whole line selecting, can we select a portion of a line, so that we can easily copy, say, a URL or git command? Thanks! :)

+3

Switching perspectives should also use perspective-specific table columns and toolbars

Thomas Singer 6 years ago 0

A panel might have different size in different perspectives. But currently widths of columns in a panel are the same in all perspectives. Which does not make much sense. E.g. I want to have sufficiently wider "Files" panel in "Review" perspective. But if column widths are the same, it is not that convenient.

Please make column width independent for different perspectives.

+3

New commit & squash command

Pierre Goiffon 6 years ago updated by David Rees 10 months ago 10

From time to time I find that one of my modifications would better fit in an unpushed commit that is not the last one. For example I've git commit A, B, C, I have modifications in my working tree, and I find that one hunk should fit in commit B.


In such situation, I :

* commit the concerned hunks

* in the commit dialog select the commit B message

* commit

* in the log view, launch an interactive rebase

* click on the "auto squash" button

* validate


Having in the commit dialog the option to directly squash staged hunks in a defined commit would be fine !

So in this example, stage the hunks, open the commit dialog, select the squash option, selection commit B, validate.

+3

Log, Files view: add information about the number of changed rows

Helena Kholkina 6 years ago updated by Marc Strapetz 6 years ago 0

Image 236

+3

Branches view: have one tree level for exactly one path-segment

Evgeny Smirnov 7 years ago updated by Oleg Sheydvasser 4 years ago 2

Currently branches and tags are combined if they differ by the last part (after the last '/') only. Instead it would be better to group them on multiple levels, for each path segment.