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

Improve "Squash" dialog consistency when executed in different places

Sync 7 years ago 0

When I do a Squash from the Journal Window, I get to choose the Authorship.  But when I squash from the Interactive Rebase dialog, I only get to edit the commit message.  


It would be nice to be consistent.  For now,  I always end the  Interactive Rebase first, then go back to Journal to squash them.

+1
Completed

Log: "Working Tree" Toolbar button in Log Windows for more obvious/easier navigation

Bernard 7 years ago updated by Marc Strapetz 6 years ago 4

I very often find myself searching through all the opened SmartGit windows.  Although I understand why it is done this way, to me, this is a major weakness of the whole SmartGit workflow (always hunting for windows).
I only very recently discovered the "Open Working Tree" option in the "Repository" menu which is a nice helper, but it is not obvious to discover and being buried in a menu makes it less optimal for navigating "back". I tried to customize the toolbar on Log windows to add this button, but there does not seem to be a way to do that.

+1

Better Key-Mapping for Conflict Solver window

Eugen Wiens 7 years ago updated by Thomas Singer 7 years ago 4

The keys that are used in the merge window are not ergonomic. The key mapping that is using by win-merge are very cool.


ALT + down: next

ALT + right: take left

ALT + left: take right

...

+1
Completed

Add stash push for stashing a subset of changed files

My-Tien 7 years ago updated by Marc Strapetz 7 years ago 4

Hello,

In the commad line you can stash a subset of changed files with:

git stash push <path-to-file>

This is useful, e.g.

- to see if changes in them are necessary for a commit

- to exclude them from a commit (sometimes quicker than staging)

- to quickly compare behaviour with and without changes in the files

- to determine if these changes caused a bug


etc.

+1
Completed

Automaticly add commit message from latest in log

soulkey4 7 years ago updated by Thomas Singer 7 years ago 1

Istead of disabling commit buttons, would be much convinient to have commit message that you previsly typed. 


(Select button is good but its also too complicated)



+1
Declined

Support for hg evolve extension

Cinderblocks 7 years ago updated by Marc Strapetz 2 years ago 1

Support for hg evolve extension. Experimental support exists on bitbucket cloud.  https://pypi.python.org/pypi/hg-evolve

+1
Completed

Implement custom (external) commands which can be accessible from menu or tool bar

Vladimir Butorin 7 years ago updated by Thomas Singer 7 years ago 5

some times we have to execute some special command (call some scripts and etc.). It will be not bad to call it by pressing one button instead of opening terminal and writing there the full command.

+1

Support floating windows/tabs.

Derrick Southerland 8 years ago 0

I'd like to be able to float, e.g., the diff tab so I can easily toss that on another monitor.


I don't want to open a full diff window because that is not tied to my active selection in the main SmartGit window.

+1

Set different encoding for each file.

Данил «Danatela» Каримов 8 years ago updated 8 years ago 2

We have files in one repository, which are encoded in several different encodings. It would be great if we had possibility to switch their encoding setting for each file like in Eclipse.

Perhaps, encoding could also be detected automatically.

+1

More distinct (colored) file statuses

Peter Slížik 8 years ago updated by Thomas Singer 8 years ago 1

In the past, I got used to the CLI git command line interface. What I like about it is that all staged files are shown in green (no matter if they were added with 'git add', 'git mv' or some other way) and all modified and untracked (non-staged) files are shown in red. This is very convenient, as one can easily see what content is stored in the Git index (stage) and what changes are made in the file system only. Switching to SmartGit, I miss these colors. I need to focus my attention of the text next to file names and actually "read" it ("Staged", "Modified", etc.)


My suggestion is that Syntevo could add an option to show the files in the "Files" view more colorful. Or, even better, to have colorful backgrounds? Or, probably, to make the icons left to the file names to use better colors? Or make the icons more distinct one from another, in general.