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 precise as possible, so users will understand what you want.


Follow the stackoverflow.com writing guidelines.

Thank you for your help!

+1

Discard: should work on renamed (missing/untracked) files

Impworks 5 years ago updated by Marc Strapetz 5 years ago 0

If a file has been renamed, Smartgit does not allow discarding it. I have to first delete the files, and then discard them in "missing state". This clearly can be automated to a single action.

+1

Reset: split into several commands

Thomas Singer 5 years ago 0

The purpose of reset hard and reset soft/mixed is completely different, the latter commands I consider are rather expert commands. It might be useful for have a plain reset command for reset hard and some other reset advanced command, so the average user will not be confused by the 3(+1) options in the current Reset dialog.

+1

Cherry-Pick dialog: add "Show only first parents" option

Robert Conde 5 years ago updated by Marc Strapetz 5 years ago 0

The "show only first parents" option in the log is great...it would be nice to have it in the cherry-pick dialog as well.

+1

Repositories view: filtering options

Peter Steiner 5 years ago updated by Marc Strapetz 5 years ago 0

It would be nice if there were filtering options for the repository pane like:

  • Show repos with incoming changes (green down arrow)
  • Show repos with outgoing changes (red up arrow)
  • Show repos not on the default branch (i.e. master)
+1

Also show the option Format Patch for files on the Working Tree at the Log Window

Bugged 5 years ago updated by Thomas Singer 5 years ago 1

Image 299

Currently, this is only available by the command line with the commands: 

  1. git diff 
  2. git diff --cached


+1

Log: usability enhancement for commands which work on commit range (e.g. Format Patch)

Bugged 5 years ago updated by Paul Du Bois 5 years ago 4

The first thing I thought about to do to create a format patch for a range of commit was to select all commits like this:

Image 269

But only after a long time I figured out how to create a format patch for a range:

  1. https://github.com/deathaxe/sublime-a-file-icon-old/issues/1#issuecomment-447904728
  2. https://github.com/gitextensions/gitextensions/issues/5923
  3. https://smartgit.userecho.com/communities/1/topics/423-functionality-to-create-a-range-of-patches-all-labelled-sequentially

Only after luckily accessing these links in sequence, I figured out SmartGit already supported the format patch feature for several commits (I was just not selecting things right https://smartgit.userecho.com/communities/1/topics/890-hard-to-understand-the-format-patch-range), because every time I did the selection a range of commits (as in the picture), the SmartGit format patch option disappeared.

+1

Log: add a low level property toopen repositories with a selection change

Bugged 5 years ago updated by Thomas Singer 5 years ago 0

I am not sure why I need to double click on it, because when I am selecting it (single click) on something, I already would like for it to open.

+1

Distributed Reviews: Allow adding review comments in log limited to subtree

Joachim Kuhnert 5 years ago 0

If the log view is restricted to a directory or file and only commits affecting this subtree are shown all review features are disabled. This makes sense for most of them like creating pull requests but it would be nice to be able to add review comments to commits and files even if the log view is filtered.

If I want for exmaple to review the changes of a specific Java package I would show the log for this folder. If I now want to make a comment I have to remeber the ID of the commit and look it up in the unrestricted log view. If I want to make a line comment I now have to select the file and scroll to the affected line and then add the comment there. A similiar case would be git blame where the log is automatically restricted to the file if I show the changes. The workflow would be more fluent if I could directly add the comment.

+1

Add "Overwrite" option to "Apply Stash"

Jeff Jensen 5 years ago updated 5 years ago 1

The auto stash feature is great when switching branches and a conflict occurs.

Regularly, I find that I want to apply the one or more stashed files with conflicts anyway, overwriting the workspace files.

I have not found an easy way of doing that; does one exist? 


If not, can we have an "Overwrite" option to Apply Stash?  This would work best with 642-cherry-pickrevert-allow-to-select-the-files-to-cherry-pickrevert on a per-stashed-file basis to limit to one file too.

+1

Log: Initial focus on last commit as option

ck 5 years ago updated by Marc Strapetz 5 years ago 1

When using the Working Tree window as primary environment, showing the current working tree state in the log again when using the "Log" button for a repo is not very helpful for two reasons:

1) This information is most likely the same that was present in the Working Tree window that opened the log

2) Selecting the last commit requires an extra step

3) SmartGit needs to assemble the list of changed / new files, although this information is most likely never needed coming from the working tree.

Therefore, it would be good to have an option to switch directly to the last commit. The working tree state still can be at the top of the list, but it should be possible that this is not the entry with default focus.