Would be great to see the tag labels also in the Journal view, especially now when it looks exactly as the Log view. Add/Remove tags in the context menu here would be also great.

Currently, diff viewer already allows to ignore whitespace changes and case changes.

I suggest to add another option to ignore empty line changes.

Changing empty lines is very common refactoring that is hard to do wrong, therefore I'd like to not see these while reviewing changes, so I can pay more attention to what's important.

It would be OK if you simply don't color these lines without changing the actual comparison algorithm, ie it would be enough for me to "don't show" vs "ignore"

A full system that allows you to use smartgit with multiple profiles/workspaces and automatically manages different .gitconfig and smartgit configurations would be awesome. Git Kraken has a very nice support for this which could be used as an example.

This is really useful and I do not think it is very difficult to add it to the right click options in the journal box

atm only i need run this on terminal (git commit --amend --date),

If you add the option to edit it from the journal box it would be great!

Custom tools could be made accessible on the Journal's context menu, this would avoid having to open the Log window to use them.

With GitHub I usually fork a project so I have the upstream project repository and my own repository. The upstream repository is read-only to me. I push to branches on my own repository and then I open a pull request from my repo to the upstream repository. Frequently I want to take the latest changes from the upstream repository and merge them into my current branch (or rebase). Currently I do all the fetching/merging/rebasing from the git command line because I don't know how to do it easily from SmartGit. I use SmartGit mainly for reviewing changes, handling conflicts and commits. If this workflow were easier in SmartGit I would not have to use any other tools. If there's an easy way to do this already, point me to the docs!

- especially portugueses

which other languages? please comment

Sometimes it is useful to compare the file (modified, staged or non-modified) with its version in another branch or commit:

git diff my-feature1 src/file.copp

This could be added into the context menu when one clicks on a file

Hi

we have a project with multiple submodules.

Between two project releases it may happen that the submodules have been updated more than once.

If I select in the log the commits of two releases, I can normally see from which state a submodule has changed to which state (the two hashes). But If I want to see which files have been changed in that submodule, I have to remember the two hashes of the submodule, open the submodule log, select the commits referred to those two hashes and finally I can see the changed files. 

I would like SmartGit to kind of automate this process, letting me see immediately the changes in the submodule between two main project commits. Important to note, I would like to open those changes in a separate log window, so that I can keep the main project log open.

Since git 2.17.0 an option was added to git fetch to remove local tags that are not present on the remote server. 

https://git-scm.com/docs/git-fetch

This option is --prune-tags and should be used with --prune.

Unfortunately there is no option in SmartGit to use this feature. 

SmartGit only offers two related options:

• "Prune obsolete remote tracked branches": this adds the --prune flag for branches ex:
  • git fetch --prune
• "Update existing and fetch new tags": this call --force with the --tags option
  • git fetch --prune --no-tags
  • git fetch --tags --force

Using both options local tags will always remain after fetching from the server and the only way to prune is via command line.

This is a useful feature for the following scenario:

1. UserA push tagA to origin
2. UserB fetch tagA from origin
3. UserA delete tagA from origin
4. UserB fetch from origin, tagA stays on his local repository.
5. UserB has no way using SmartGit to know that tagA was deleted. His next push will push tagA again.

Thank you